Re: [DRAFT] What the new Status Pages potentially look like

2017-06-16 Thread John D. Ament
On Thu, Jun 15, 2017 at 3:50 PM Jim Apple wrote: > Thank you for the responses. > > >> 5. Make sure the Whimsy page applies to all projects. For instance, > >> Impala releases are source tarballs, so if "Binary Distribution > >> Licensing" means something about a

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-15 Thread Jim Apple
Thank you for the responses. >> 5. Make sure the Whimsy page applies to all projects. For instance, >> Impala releases are source tarballs, so if "Binary Distribution >> Licensing" means something about a non-source-tarball release >> artefact, it's not meaningful for Impala. >> > > Hmm that's

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-15 Thread John D. Ament
Jim, Thanks for the input! On Thu, Jun 15, 2017 at 1:22 PM Jim Apple wrote: > Here are some suggestions: > > 1. Only make this the reporting structure for new podlings. > Grandfather in old podlings to the old structure, since they may > already have workflows built

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-15 Thread Sam Ruby
On Thu, Jun 15, 2017 at 1:21 PM, Jim Apple wrote: > Here are some suggestions: > > 1. Only make this the reporting structure for new podlings. > Grandfather in old podlings to the old structure, since they may > already have workflows built around it. Impala does. We don't

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-15 Thread Jim Apple
Here are some suggestions: 1. Only make this the reporting structure for new podlings. Grandfather in old podlings to the old structure, since they may already have workflows built around it. Impala does. 2. Provide a clear description of the meaning and formatting of each field in comments on

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-14 Thread Sam Ruby
On Tue, Jun 13, 2017 at 9:04 PM, John D. Ament wrote: > Jim, > > For your specific cases, if all you want is to remove red text: > > - for :sga: enter the date in -MM-DD format of when the ASF Secretary > acknowledged your SGA. Based on the records I have its

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-14 Thread Dale LaBossiere
John, can you confirm appropriate values for Edgent in order to clear up all the red under “Licensing”? From http://incubator.apache.org/projects/edgent.html these seem to be the appropriate values (from that copyrights section as well as 1.0.0 release date of 2016-12-15): :sga:2016-03-11

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-13 Thread John D. Ament
Jim, For your specific cases, if all you want is to remove red text: - for :sga: enter the date in -MM-DD format of when the ASF Secretary acknowledged your SGA. Based on the records I have its 2016-03-15 - For the :asfCopyright: and :distributionRights: attributes, I would use 2017-01-20

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-13 Thread Jim Apple
I'm confused. The message to podlings@ said "If you're not sure what to fill out, feel free to reach out." It sounds like there is no set way yet to fill it out. What can I do to get the bolded, red, inaccurate scare messages off of our whimsy page? On Tue, Jun 13, 2017 at 5:30 PM, John D.

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-13 Thread John D. Ament
Good points Dave. To be honest, since this is a prototype I don't have answers any more than "If you think it should do that, we can make it do that" What I did have in mind: --- :issueTracker: jira|github|bugzilla :wiki: if using confluence, their space key :jira: if using jira, their issue

Re: [DRAFT] What the new Status Pages potentially look like

2017-06-13 Thread Dave Fisher
Hi John - These are excellent questions. I see each of these as being tuples of various kinds. For example :sga: could have multiple grants each of which has a date and a file name to refer to in the foundation records. The path to the source repository is missing completely. Some of these