mwiki file format - rough #1
Comments
|
HI there!
Thanks for getting back so soon.
HTML/PDF thing seems wrong to me. We are going to need to figure out a
better workflow. Two main options
1) you fork the repo, make changes, I git pull them
2) you do a writeup (email, google doc, whatever), essentially in "helpful
feedback" form, and I do the integrating
I think 1 is more elegant in theory, but 2 is more practical and we should
be doing that for now. Reason being, I am doing so many little markdown
edits that git merge has potential to be scary, and I would rather not go
there.
So let's go with option 2. So, I will want the following, in standalone
writeup format
* a list of glossary candidates
* and/or zen mind feedback
We don't have to do another call today, but if you think it would be
helpful I can make some time before noon EST. (I might be at the gym but
that's ok if not a long call.)
I hope this makes sense, and is helpful!
Cheers,
Thomas.
…On Tue, Oct 20, 2020 at 2:51 AM Brian M Hamlin ***@***.***> wrote:
prep for glossary -- source is HTML, print to PDF; rough format changes
plus bold on GLOSSARY candidate terms;
bip-format-0.pdf
<https://github.com/tphyahoo/bip-thomashartman-op_energy/files/5406778/bip-format-0.pdf>
aome formatting on math / code snippets.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAKOISIJEFAC7MRHOGOOLSLUXQDANCNFSM4SXWFLJA>
.
|
|
Can you review pages 1-3 (through "Summary" section). Made a bunch of
changes, thinking about this glossary issue. (More careful definition of
units.)
Thoughts?
On Tue, Oct 20, 2020 at 9:21 AM Thomas Hartman <[email protected]>
wrote:
… HI there!
Thanks for getting back so soon.
HTML/PDF thing seems wrong to me. We are going to need to figure out a
better workflow. Two main options
1) you fork the repo, make changes, I git pull them
2) you do a writeup (email, google doc, whatever), essentially in "helpful
feedback" form, and I do the integrating
I think 1 is more elegant in theory, but 2 is more practical and we should
be doing that for now. Reason being, I am doing so many little markdown
edits that git merge has potential to be scary, and I would rather not go
there.
So let's go with option 2. So, I will want the following, in standalone
writeup format
* a list of glossary candidates
* and/or zen mind feedback
We don't have to do another call today, but if you think it would be
helpful I can make some time before noon EST. (I might be at the gym but
that's ok if not a long call.)
I hope this makes sense, and is helpful!
Cheers,
Thomas.
On Tue, Oct 20, 2020 at 2:51 AM Brian M Hamlin ***@***.***>
wrote:
> prep for glossary -- source is HTML, print to PDF; rough format changes
> plus bold on GLOSSARY candidate terms;
>
> bip-format-0.pdf
> <https://github.com/tphyahoo/bip-thomashartman-op_energy/files/5406778/bip-format-0.pdf>
>
> aome formatting on math / code snippets.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#1>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAAAKOISIJEFAC7MRHOGOOLSLUXQDANCNFSM4SXWFLJA>
> .
>
|
|
I cut the length of the bip nearly in half by moving more complicated
topics to whitepaper.
I realize you may have already started diving in to the stuff I segregated
away, but moving forward: focus on what is left in the bip, and we'll
circle back to whitepaper stuff later?
the shortened bip, 13 pages instead of 20:
https://github.com/tphyahoo/bip-thomashartman-op_energy/blob/master/bip-op_energy.mediawiki
(has links to whitepaper)
On Tue, Oct 20, 2020 at 3:43 PM Thomas Hartman <[email protected]>
wrote:
… Can you review pages 1-3 (through "Summary" section). Made a bunch of
changes, thinking about this glossary issue. (More careful definition of
units.)
Thoughts?
On Tue, Oct 20, 2020 at 9:21 AM Thomas Hartman ***@***.***>
wrote:
> HI there!
>
> Thanks for getting back so soon.
>
> HTML/PDF thing seems wrong to me. We are going to need to figure out a
> better workflow. Two main options
>
> 1) you fork the repo, make changes, I git pull them
> 2) you do a writeup (email, google doc, whatever), essentially in
> "helpful feedback" form, and I do the integrating
>
> I think 1 is more elegant in theory, but 2 is more practical and we
> should be doing that for now. Reason being, I am doing so many little
> markdown edits that git merge has potential to be scary, and I would rather
> not go there.
>
> So let's go with option 2. So, I will want the following, in standalone
> writeup format
>
> * a list of glossary candidates
> * and/or zen mind feedback
>
> We don't have to do another call today, but if you think it would be
> helpful I can make some time before noon EST. (I might be at the gym but
> that's ok if not a long call.)
>
> I hope this makes sense, and is helpful!
>
> Cheers,
> Thomas.
>
>
>
>
>
>
> On Tue, Oct 20, 2020 at 2:51 AM Brian M Hamlin ***@***.***>
> wrote:
>
>> prep for glossary -- source is HTML, print to PDF; rough format changes
>> plus bold on GLOSSARY candidate terms;
>>
>> bip-format-0.pdf
>> <https://github.com/tphyahoo/bip-thomashartman-op_energy/files/5406778/bip-format-0.pdf>
>>
>> aome formatting on math / code snippets.
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub
>> <#1>, or
>> unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/AAAAKOISIJEFAC7MRHOGOOLSLUXQDANCNFSM4SXWFLJA>
>> .
>>
>
|
|
actually 8 pages!
On Wed, Oct 21, 2020 at 7:59 AM Thomas Hartman <[email protected]>
wrote:
… I cut the length of the bip nearly in half by moving more complicated
topics to whitepaper.
I realize you may have already started diving in to the stuff I segregated
away, but moving forward: focus on what is left in the bip, and we'll
circle back to whitepaper stuff later?
the shortened bip, 13 pages instead of 20:
https://github.com/tphyahoo/bip-thomashartman-op_energy/blob/master/bip-op_energy.mediawiki
(has links to whitepaper)
On Tue, Oct 20, 2020 at 3:43 PM Thomas Hartman ***@***.***>
wrote:
> Can you review pages 1-3 (through "Summary" section). Made a bunch of
> changes, thinking about this glossary issue. (More careful definition of
> units.)
>
> Thoughts?
>
> On Tue, Oct 20, 2020 at 9:21 AM Thomas Hartman ***@***.***>
> wrote:
>
>> HI there!
>>
>> Thanks for getting back so soon.
>>
>> HTML/PDF thing seems wrong to me. We are going to need to figure out a
>> better workflow. Two main options
>>
>> 1) you fork the repo, make changes, I git pull them
>> 2) you do a writeup (email, google doc, whatever), essentially in
>> "helpful feedback" form, and I do the integrating
>>
>> I think 1 is more elegant in theory, but 2 is more practical and we
>> should be doing that for now. Reason being, I am doing so many little
>> markdown edits that git merge has potential to be scary, and I would rather
>> not go there.
>>
>> So let's go with option 2. So, I will want the following, in standalone
>> writeup format
>>
>> * a list of glossary candidates
>> * and/or zen mind feedback
>>
>> We don't have to do another call today, but if you think it would be
>> helpful I can make some time before noon EST. (I might be at the gym but
>> that's ok if not a long call.)
>>
>> I hope this makes sense, and is helpful!
>>
>> Cheers,
>> Thomas.
>>
>>
>>
>>
>>
>>
>> On Tue, Oct 20, 2020 at 2:51 AM Brian M Hamlin ***@***.***>
>> wrote:
>>
>>> prep for glossary -- source is HTML, print to PDF; rough format changes
>>> plus bold on GLOSSARY candidate terms;
>>>
>>> bip-format-0.pdf
>>> <https://github.com/tphyahoo/bip-thomashartman-op_energy/files/5406778/bip-format-0.pdf>
>>>
>>> aome formatting on math / code snippets.
>>>
>>> —
>>> You are receiving this because you are subscribed to this thread.
>>> Reply to this email directly, view it on GitHub
>>> <#1>, or
>>> unsubscribe
>>> <https://github.com/notifications/unsubscribe-auth/AAAAKOISIJEFAC7MRHOGOOLSLUXQDANCNFSM4SXWFLJA>
>>> .
>>>
>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
prep for glossary -- source is HTML, print to PDF; rough format changes plus bold on GLOSSARY candidate terms;
bip-format-0.pdf
aome formatting on math / code snippets.
The text was updated successfully, but these errors were encountered: