On Wed, May 22, 2019 at 10:26 AM Justin Mclean wrote:
>
> Hi,
>
> > Doesn't the new Markdown format help with that?
>
> I hope it will but:
> a) Messy markdown with inconsistent formatting can still look good.
> b) Some podlings submit at the last minutes and ignore formatting.
> c) Some podlings
On Wed, May 22, 2019 at 4:27 PM Justin Mclean wrote:
> ...I'm not sure the board will be viewing the results of the markdown but
> just the raw text???...
I think you need plaintext for the Board report but my idea was to get
that by copying and pasting the output of the Markdown conversion:
Hi,
> Doesn't the new Markdown format help with that?
I hope it will but:
a) Messy markdown with inconsistent formatting can still look good.
b) Some podlings submit at the last minutes and ignore formatting.
c) Some podlings tend to copy and paste the last report and modify and may
miss/alter
Hi,
On Wed, May 22, 2019 at 3:19 PM Justin Mclean wrote:
> ...Reflow so that they are human readable is a little hard to write down. :-)
> Mostly it because of the wide
> variation of formatting podlings submit their reports ...
Doesn't the new Markdown format help with that? I experimented a
Hi,
> The duplication problem was fixed by changing the incubator report to
> not have lines starting with dashes surrounding the TOC.
I’m not 100% sure it fixed, as it happened again after that. It’s happened 4 or
5 times from memory, each time it need to be fixed manually.
> There actually
On Wed, May 22, 2019 at 8:28 AM Justin Mclean wrote:
>
> Hi,
>
> > - Whimsy likes 80 column linewraps. It will only rewrap the current
> > report if you push the rewrap button and then commit. It doesn't ever
> > wrap long URLs.
>
> Currently that severely breaks the incubator report so I don’t
Hi,
> - Whimsy likes 80 column linewraps. It will only rewrap the current
> report if you push the rewrap button and then commit. It doesn't ever
> wrap long URLs.
Currently that severely breaks the incubator report so I don’t use it. Also any
edits to the incubator report in Whimsey
Bertrand Delacretaz wrote on 5/22/19 6:09 AM:
> On Wed, May 22, 2019 at 11:46 AM Justin Mclean
> wrote:
>> ...It’s still unclear to me how Whimsy will render this, guess we find out
>> when we submit it?..
>
> I think the core of the Board agenda is the text file in svn, that's
> what needs to
Hi,
> I think the core of the Board agenda is the text file in svn, that's
> what needs to be clean AFAIK.
Yep and IMO a little bit of markdown in that doesn’t make it any harder to read.
Thanks,
Justin
-
To unsubscribe,
Hi,
On Wed, May 22, 2019 at 11:46 AM Justin Mclean wrote:
> ...It’s still unclear to me how Whimsy will render this, guess we find out
> when we submit it?..
I think the core of the Board agenda is the text file in svn, that's
what needs to be clean AFAIK.
-Bertrand
Hi,
> Perhaps next time, save the before and after and the whimsy team can
> take a look at how much of it can be automated.
It’s all in versions so that easy to do.
IMO Some could possible be automated, somethings are going to be very hard to
do so as it would need to selectively join or
On Wed, May 22, 2019 at 5:46 AM Justin Mclean wrote:
>
> Hi,
>
> > Do you then mean to run "fold -w 76 cat -s" on the formatted Markdown
> > to prepare it for the Board report?
>
> Yes, as your experiment is still of use. Someone somewhere is still going to
> view it in text form.
>
> It’s still
Hi,
> Do you then mean to run "fold -w 76 cat -s" on the formatted Markdown
> to prepare it for the Board report?
Yes, as your experiment is still of use. Someone somewhere is still going to
view it in text form.
It’s still unclear to me how Whimsy will render this, guess we find out when we
On Wed, May 22, 2019 at 10:18 AM Justin Mclean wrote:
> ...So INFRA kindly installed a markdown macro for confluence so you can now
> see
> the incubator report with some formatting when you edit it. [1]..
Cool! I have removed my formatting experiment,
Hi,
So INFRA kindly installed a markdown macro for confluence so you can now see
the incubator report with some formatting when you edit it. [1]
Thanks,
Justin
1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
Hi,
> Please remove Dubbo since it graduated.
Will do, the data it auto generated as you know, the podling.xml file hadn’t
been updated when it was generated (or the graduation announced).
Thanks,
Justin
-
To unsubscribe,
Hi Justin,
Please remove Dubbo since it graduated.
Regards,
Dave
Sent from my iPhone
> On May 21, 2019, at 4:57 PM, Dave Fisher wrote:
>
> Hi Justin,
>
> You gave me four to shepherd again and missed Drew.
>
> Thanks,
> Dave
>
>> On May 21, 2019, at 4:49 PM, Justin Mclean wrote:
>>
>>
Hi,
I also asked for a mark-down plug tube installed in confluence so podlings can
see / preview their edits.
https://issues.apache.org/jira/browse/INFRA-18439
Thanks,
Justin
-
To unsubscribe, e-mail:
Hi,
> - checkboxes
Seems that here are not standard markdown but supported by github’s (and a
couple of other places) markdown. So not sure how useful that will be.
Thanks,
Justin
-
To unsubscribe, e-mail:
Hi Justin,
You gave me four to shepherd again and missed Drew.
Thanks,
Dave
> On May 21, 2019, at 4:49 PM, Justin Mclean wrote:
>
> Hi,
>
> It been suggested we use markdown for the incubator reports. I modified the
> this months report [1] to have:
> - a table of contents
> - headings
> -
Hi,
It been suggested we use markdown for the incubator reports. I modified the
this months report [1] to have:
- a table of contents
- headings
- checkboxes
Is there anything else you basic format needd?
Thanks,
Justin
1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
Hi， Justin，Thanks for your suggestion
I will keep in mind for next report.
Thanks
在 2019/5/20 下午6:55，“Justin Mclean” 写入:
Hi,
Some issues I see with the format:
This:
Three most important issues to address in the move towards graduation:
1. We begin to
Justin Mclean wrote on 5/20/19 9:04 AM:
...snip...>> Or we can improve the script or maybe even move to Markdown
for the
>> input to have more control, if you think this would help.
>
> Markdown might help the board in reviews (but not 100% sure about that), but
> it would be more work for the
Hi,
> It doesn't look too bad to me - my point would be that if people can
> see the final formatted result at that URL they can fix their reports.
> themselves (like for the example you give below) and you don't have to
> do that.
I'm all for something that encourages podlings to correctly
Hi Justin,
I've put your test content in and added cat -s, the formatted result
is at http://incubator.apache.org/report.html
It doesn't look too bad to me - my point would be that if people can
see the final formatted result at that URL they can fix their reports
themselves (like for the
Hi,
Or perhaps another way of looking at it, is that given I already do this (and
hand edit):
fold -w 76 -s $1 | cat -s
You can probably skip that step for the final report, but then I’m not sure
what this result gives over the existing confluence page. [1]
Unless you have something more in
Hi,
Some issues I see with the format:
This:
Three most important issues to address in the move towards graduation:
1. We begin to prepare an apache release, including prepare for unified
License/Copyright, clean dependencies.
2. We depend on npsr’ time, it is MPL/LGPL license, we need to
Hi,
The "fold -s -w 76" will breaks on long line e.g URLs. I do something similar
and need to manually fix that, I’d also add "| cat -s” to tame extra blank
lines.
Not to dampen your enthusiasm, but their one huge assumption here and that’s
you usually taken the result of what was hand
Hi,
It seems like there was some trouble and manual work to generate the
Board report since switching to https://cwiki.apache.org/incubator
As an experiment that should make this easier, I have created a small
pipeline that starts from a text file in Git [1], uses a script to
sanitize that file
29 matches
Mail list logo
