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

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Dave Fisher-5
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 items could be transitory. For example distributionRights may be confirmed but then something is added which negates those rights until the issue is cleared up.

I wonder if it makes sense to provide links to email threads and/or Wiki pages with the details?

Regards,
Dave

> On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]> wrote:
>
> What format of data is expected in the fields? Impala's new status
> page SVN config file
> <https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml>
> is:
>
> ---
> :issueTracker: jira
> :wiki: IMPALA
> :jira: IMPALA
> :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> :asfCopyright:
> :distributionRights:
> :ipClearance:
> :sga:
> :website: http://impala.incubator.apache.org
> :graduationDate:
> :resolution:
>
> I do not know how to fill out asfCopyright, distributionRights,
> ipClearance, or sga. Note that I believe I understand what these
> things ARE, I just don't know how to word them -- "asfCopyright: OK"?
>
> I also don't know which one(s) correspond to the bold red "No Release
> Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
> has had a couple of ASF releases.
>
> On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <[hidden email]> wrote:
>> All,
>>
>> We're piloting a new format for the podling status pages.  Specifically,
>> the current status page leaves a lot to be desired - it's basically crafted
>> html, there's no structure and its hard to find missing items.  The end
>> goal is to have a web form editable in Whimsy, but until we get more input
>> on what the content looks like I don't want to make changes like that.  I'm
>> asking at this point for podlings to take a look at the status output,
>> potentially update their own content, and see if they like the output.
>>
>> If you navigate to https://whimsy.apache.org/roster/ppmc/ (authentication
>> is via your ASF committer username/password) and find your podling, you'll
>> see your current roster as well as your current status information.
>>
>> The status pages can be found in SVN at this directory
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>>
>> Some more information can be found at
>> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
>>
>> If you're not sure what to fill out, feel free to reach out.
>>
>> John


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

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 key (though I suppose this can be
multiple)
:proposal: link to the proposal page.
:asfCopyright: the date that we confirmed ASF copyright headers on the
source code (e.g. the first time a source release passed without any issues)
:distributionRights: the date that we confirmed the resulting binary
satisfied our release policies (e.g. the first time a release included a
binary without any issues)
:ipClearance: a link to the IP Clearance page for this podling.  I guess
this can be multiple?
:sga: date in which a SGA was received
:website: http://impala.incubator.apache.org
:graduationDate: to be filled in when the podling graduates
:resolution: tlp|subproject , if subproject the TLP should be in here
somehwere.  We may want to track as "sponsor."

I can draft this up on a wiki page to gain more input.  What do you think
about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
work through it?  I had a few more questions in line.

On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher <[hidden email]> wrote:

> 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.
>
>
We don't usually expose the file name to people outside members, so I'm not
sure this would be useful.  Multiple dates are also not common.


> The path to the source repository is missing completely.
>

Which source repository?  The podlings?  I have a prototype for gitbox
podlings and think I can make it work for ASF git as well.  For SVN, we can
assume default or have a list of values.


>
> Some of these items could be transitory. For example distributionRights
> may be confirmed but then something is added which negates those rights
> until the issue is cleared up.
>
>
+1


> I wonder if it makes sense to provide links to email threads and/or Wiki
> pages with the details?
>
> Regards,
> Dave
>
> > On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]> wrote:
> >
> > What format of data is expected in the fields? Impala's new status
> > page SVN config file
> > <
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
> >
> > is:
> >
> > ---
> > :issueTracker: jira
> > :wiki: IMPALA
> > :jira: IMPALA
> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> > :asfCopyright:
> > :distributionRights:
> > :ipClearance:
> > :sga:
> > :website: http://impala.incubator.apache.org
> > :graduationDate:
> > :resolution:
> >
> > I do not know how to fill out asfCopyright, distributionRights,
> > ipClearance, or sga. Note that I believe I understand what these
> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
> >
> > I also don't know which one(s) correspond to the bold red "No Release
> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
> > has had a couple of ASF releases.
> >
> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <[hidden email]>
> wrote:
> >> All,
> >>
> >> We're piloting a new format for the podling status pages.  Specifically,
> >> the current status page leaves a lot to be desired - it's basically
> crafted
> >> html, there's no structure and its hard to find missing items.  The end
> >> goal is to have a web form editable in Whimsy, but until we get more
> input
> >> on what the content looks like I don't want to make changes like that.
> I'm
> >> asking at this point for podlings to take a look at the status output,
> >> potentially update their own content, and see if they like the output.
> >>
> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
> (authentication
> >> is via your ASF committer username/password) and find your podling,
> you'll
> >> see your current roster as well as your current status information.
> >>
> >> The status pages can be found in SVN at this directory
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> >>
> >> Some more information can be found at
> >>
> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
> >>
> >> If you're not sure what to fill out, feel free to reach out.
> >>
> >> John
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

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. Ament <[hidden email]> wrote:

> 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 key (though I suppose this can be
> multiple)
> :proposal: link to the proposal page.
> :asfCopyright: the date that we confirmed ASF copyright headers on the
> source code (e.g. the first time a source release passed without any issues)
> :distributionRights: the date that we confirmed the resulting binary
> satisfied our release policies (e.g. the first time a release included a
> binary without any issues)
> :ipClearance: a link to the IP Clearance page for this podling.  I guess
> this can be multiple?
> :sga: date in which a SGA was received
> :website: http://impala.incubator.apache.org
> :graduationDate: to be filled in when the podling graduates
> :resolution: tlp|subproject , if subproject the TLP should be in here
> somehwere.  We may want to track as "sponsor."
>
> I can draft this up on a wiki page to gain more input.  What do you think
> about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
> work through it?  I had a few more questions in line.
>
> On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher <[hidden email]> wrote:
>
>> 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.
>>
>>
> We don't usually expose the file name to people outside members, so I'm not
> sure this would be useful.  Multiple dates are also not common.
>
>
>> The path to the source repository is missing completely.
>>
>
> Which source repository?  The podlings?  I have a prototype for gitbox
> podlings and think I can make it work for ASF git as well.  For SVN, we can
> assume default or have a list of values.
>
>
>>
>> Some of these items could be transitory. For example distributionRights
>> may be confirmed but then something is added which negates those rights
>> until the issue is cleared up.
>>
>>
> +1
>
>
>> I wonder if it makes sense to provide links to email threads and/or Wiki
>> pages with the details?
>>
>> Regards,
>> Dave
>>
>> > On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]> wrote:
>> >
>> > What format of data is expected in the fields? Impala's new status
>> > page SVN config file
>> > <
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
>> >
>> > is:
>> >
>> > ---
>> > :issueTracker: jira
>> > :wiki: IMPALA
>> > :jira: IMPALA
>> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
>> > :asfCopyright:
>> > :distributionRights:
>> > :ipClearance:
>> > :sga:
>> > :website: http://impala.incubator.apache.org
>> > :graduationDate:
>> > :resolution:
>> >
>> > I do not know how to fill out asfCopyright, distributionRights,
>> > ipClearance, or sga. Note that I believe I understand what these
>> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
>> >
>> > I also don't know which one(s) correspond to the bold red "No Release
>> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
>> > has had a couple of ASF releases.
>> >
>> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <[hidden email]>
>> wrote:
>> >> All,
>> >>
>> >> We're piloting a new format for the podling status pages.  Specifically,
>> >> the current status page leaves a lot to be desired - it's basically
>> crafted
>> >> html, there's no structure and its hard to find missing items.  The end
>> >> goal is to have a web form editable in Whimsy, but until we get more
>> input
>> >> on what the content looks like I don't want to make changes like that.
>> I'm
>> >> asking at this point for podlings to take a look at the status output,
>> >> potentially update their own content, and see if they like the output.
>> >>
>> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
>> (authentication
>> >> is via your ASF committer username/password) and find your podling,
>> you'll
>> >> see your current roster as well as your current status information.
>> >>
>> >> The status pages can be found in SVN at this directory
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>> >>
>> >> Some more information can be found at
>> >>
>> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
>> >>
>> >> If you're not sure what to fill out, feel free to reach out.
>> >>
>> >> John
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

John D. Ament-2
Jim,

For your specific cases, if all you want is to remove red text:

- for :sga: enter the date in YYYY-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 as that's the day of the results of 2.8 which was the first
release to have no issues during review.

But please do continue to provide input, want to make sure we're building
something useful, not a pain.

HTH,

John

On Tue, Jun 13, 2017 at 8:52 PM Jim Apple <[hidden email]> wrote:

> 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. Ament <[hidden email]>
> wrote:
> > 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 key (though I suppose this can be
> > multiple)
> > :proposal: link to the proposal page.
> > :asfCopyright: the date that we confirmed ASF copyright headers on the
> > source code (e.g. the first time a source release passed without any
> issues)
> > :distributionRights: the date that we confirmed the resulting binary
> > satisfied our release policies (e.g. the first time a release included a
> > binary without any issues)
> > :ipClearance: a link to the IP Clearance page for this podling.  I guess
> > this can be multiple?
> > :sga: date in which a SGA was received
> > :website: http://impala.incubator.apache.org
> > :graduationDate: to be filled in when the podling graduates
> > :resolution: tlp|subproject , if subproject the TLP should be in here
> > somehwere.  We may want to track as "sponsor."
> >
> > I can draft this up on a wiki page to gain more input.  What do you think
> > about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
> > work through it?  I had a few more questions in line.
> >
> > On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher <[hidden email]>
> wrote:
> >
> >> 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.
> >>
> >>
> > We don't usually expose the file name to people outside members, so I'm
> not
> > sure this would be useful.  Multiple dates are also not common.
> >
> >
> >> The path to the source repository is missing completely.
> >>
> >
> > Which source repository?  The podlings?  I have a prototype for gitbox
> > podlings and think I can make it work for ASF git as well.  For SVN, we
> can
> > assume default or have a list of values.
> >
> >
> >>
> >> Some of these items could be transitory. For example distributionRights
> >> may be confirmed but then something is added which negates those rights
> >> until the issue is cleared up.
> >>
> >>
> > +1
> >
> >
> >> I wonder if it makes sense to provide links to email threads and/or Wiki
> >> pages with the details?
> >>
> >> Regards,
> >> Dave
> >>
> >> > On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]> wrote:
> >> >
> >> > What format of data is expected in the fields? Impala's new status
> >> > page SVN config file
> >> > <
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
> >> >
> >> > is:
> >> >
> >> > ---
> >> > :issueTracker: jira
> >> > :wiki: IMPALA
> >> > :jira: IMPALA
> >> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> >> > :asfCopyright:
> >> > :distributionRights:
> >> > :ipClearance:
> >> > :sga:
> >> > :website: http://impala.incubator.apache.org
> >> > :graduationDate:
> >> > :resolution:
> >> >
> >> > I do not know how to fill out asfCopyright, distributionRights,
> >> > ipClearance, or sga. Note that I believe I understand what these
> >> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
> >> >
> >> > I also don't know which one(s) correspond to the bold red "No Release
> >> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
> >> > has had a couple of ASF releases.
> >> >
> >> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <[hidden email]
> >
> >> wrote:
> >> >> All,
> >> >>
> >> >> We're piloting a new format for the podling status pages.
> Specifically,
> >> >> the current status page leaves a lot to be desired - it's basically
> >> crafted
> >> >> html, there's no structure and its hard to find missing items.  The
> end
> >> >> goal is to have a web form editable in Whimsy, but until we get more
> >> input
> >> >> on what the content looks like I don't want to make changes like
> that.
> >> I'm
> >> >> asking at this point for podlings to take a look at the status
> output,
> >> >> potentially update their own content, and see if they like the
> output.
> >> >>
> >> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
> >> (authentication
> >> >> is via your ASF committer username/password) and find your podling,
> >> you'll
> >> >> see your current roster as well as your current status information.
> >> >>
> >> >> The status pages can be found in SVN at this directory
> >> >>
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> >> >>
> >> >> Some more information can be found at
> >> >>
> >>
> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
> >> >>
> >> >> If you're not sure what to fill out, feel free to reach out.
> >> >>
> >> >> John
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Dale LaBossiere-2
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
:asfCopyright:2016-12-15
:distributionRights:2016-12-15

Next question: how to update the info?  If it’s “a mentor must do it”, can you please handle it :-)

Thanks,
— Dale


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Sam Ruby
In reply to this post by John D. Ament-2
On Tue, Jun 13, 2017 at 9:04 PM, John D. Ament <[hidden email]> wrote:

> Jim,
>
> For your specific cases, if all you want is to remove red text:
>
> - for :sga: enter the date in YYYY-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 as that's the day of the results of 2.8 which was the first
> release to have no issues during review.
>
> But please do continue to provide input, want to make sure we're building
> something useful, not a pain.

Suggestion: let's start talking about how we should make the roster
page prompt for, validate, and apply any changes.

As in, for every field that is editable, there should be a way to
bring up an HTML form.  That form should contain explanatory text, and
perform validations.  Submitting that form should update the
appropriate YAML file in svn, and potentially notify various lists of
the change.

If people can provide the information above for a single field, I can
implement that change for the first field and people can use that as
an example to do the same for other fields.

> HTH,
>
> John

- Sam Ruby

> On Tue, Jun 13, 2017 at 8:52 PM Jim Apple <[hidden email]> wrote:
>
>> 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. Ament <[hidden email]>
>> wrote:
>> > 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 key (though I suppose this can be
>> > multiple)
>> > :proposal: link to the proposal page.
>> > :asfCopyright: the date that we confirmed ASF copyright headers on the
>> > source code (e.g. the first time a source release passed without any
>> issues)
>> > :distributionRights: the date that we confirmed the resulting binary
>> > satisfied our release policies (e.g. the first time a release included a
>> > binary without any issues)
>> > :ipClearance: a link to the IP Clearance page for this podling.  I guess
>> > this can be multiple?
>> > :sga: date in which a SGA was received
>> > :website: http://impala.incubator.apache.org
>> > :graduationDate: to be filled in when the podling graduates
>> > :resolution: tlp|subproject , if subproject the TLP should be in here
>> > somehwere.  We may want to track as "sponsor."
>> >
>> > I can draft this up on a wiki page to gain more input.  What do you think
>> > about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
>> > work through it?  I had a few more questions in line.
>> >
>> > On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher <[hidden email]>
>> wrote:
>> >
>> >> 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.
>> >>
>> >>
>> > We don't usually expose the file name to people outside members, so I'm
>> not
>> > sure this would be useful.  Multiple dates are also not common.
>> >
>> >
>> >> The path to the source repository is missing completely.
>> >>
>> >
>> > Which source repository?  The podlings?  I have a prototype for gitbox
>> > podlings and think I can make it work for ASF git as well.  For SVN, we
>> can
>> > assume default or have a list of values.
>> >
>> >
>> >>
>> >> Some of these items could be transitory. For example distributionRights
>> >> may be confirmed but then something is added which negates those rights
>> >> until the issue is cleared up.
>> >>
>> >>
>> > +1
>> >
>> >
>> >> I wonder if it makes sense to provide links to email threads and/or Wiki
>> >> pages with the details?
>> >>
>> >> Regards,
>> >> Dave
>> >>
>> >> > On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]> wrote:
>> >> >
>> >> > What format of data is expected in the fields? Impala's new status
>> >> > page SVN config file
>> >> > <
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
>> >> >
>> >> > is:
>> >> >
>> >> > ---
>> >> > :issueTracker: jira
>> >> > :wiki: IMPALA
>> >> > :jira: IMPALA
>> >> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
>> >> > :asfCopyright:
>> >> > :distributionRights:
>> >> > :ipClearance:
>> >> > :sga:
>> >> > :website: http://impala.incubator.apache.org
>> >> > :graduationDate:
>> >> > :resolution:
>> >> >
>> >> > I do not know how to fill out asfCopyright, distributionRights,
>> >> > ipClearance, or sga. Note that I believe I understand what these
>> >> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
>> >> >
>> >> > I also don't know which one(s) correspond to the bold red "No Release
>> >> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
>> >> > has had a couple of ASF releases.
>> >> >
>> >> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <[hidden email]
>> >
>> >> wrote:
>> >> >> All,
>> >> >>
>> >> >> We're piloting a new format for the podling status pages.
>> Specifically,
>> >> >> the current status page leaves a lot to be desired - it's basically
>> >> crafted
>> >> >> html, there's no structure and its hard to find missing items.  The
>> end
>> >> >> goal is to have a web form editable in Whimsy, but until we get more
>> >> input
>> >> >> on what the content looks like I don't want to make changes like
>> that.
>> >> I'm
>> >> >> asking at this point for podlings to take a look at the status
>> output,
>> >> >> potentially update their own content, and see if they like the
>> output.
>> >> >>
>> >> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
>> >> (authentication
>> >> >> is via your ASF committer username/password) and find your podling,
>> >> you'll
>> >> >> see your current roster as well as your current status information.
>> >> >>
>> >> >> The status pages can be found in SVN at this directory
>> >> >>
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>> >> >>
>> >> >> Some more information can be found at
>> >> >>
>> >>
>> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
>> >> >>
>> >> >> If you're not sure what to fill out, feel free to reach out.
>> >> >>
>> >> >> John
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Jim Apple
In reply to this post by John D. Ament-2
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 the YAML file itself.

3. Provide guidance on how long it takes from SVN checkin to whimsy
render change.

4. Use git, not SVN

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.

6. Give the fields on the whimsy page names that correspond,
one-to-one, with the YAML fields.

7. Give the Whimsy page headers more specific meanings. "Confirmation
of ASF Copyright Headers on Source Code on" could mean confirmation by
any number of people or committees. Which one is meant by this phrase?
If it's the IPMC, and the first approved release is what is meant by
this, change the name to "First Apache release" or something.

8. Provide the ability to lookup the information required to fill out
the status page. How can a podling find out when the SGA was received?
Please remember that podling personnel can change during incubation.

On Tue, Jun 13, 2017 at 6:04 PM, John D. Ament <[hidden email]> wrote:

> Jim,
>
> For your specific cases, if all you want is to remove red text:
>
> - for :sga: enter the date in YYYY-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 as that's the day of the results of 2.8 which was the first
> release to have no issues during review.
>
> But please do continue to provide input, want to make sure we're building
> something useful, not a pain.
>
> HTH,
>
> John
>
> On Tue, Jun 13, 2017 at 8:52 PM Jim Apple <[hidden email]> wrote:
>
>> 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. Ament <[hidden email]>
>> wrote:
>> > 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 key (though I suppose this can be
>> > multiple)
>> > :proposal: link to the proposal page.
>> > :asfCopyright: the date that we confirmed ASF copyright headers on the
>> > source code (e.g. the first time a source release passed without any
>> issues)
>> > :distributionRights: the date that we confirmed the resulting binary
>> > satisfied our release policies (e.g. the first time a release included a
>> > binary without any issues)
>> > :ipClearance: a link to the IP Clearance page for this podling.  I guess
>> > this can be multiple?
>> > :sga: date in which a SGA was received
>> > :website: http://impala.incubator.apache.org
>> > :graduationDate: to be filled in when the podling graduates
>> > :resolution: tlp|subproject , if subproject the TLP should be in here
>> > somehwere.  We may want to track as "sponsor."
>> >
>> > I can draft this up on a wiki page to gain more input.  What do you think
>> > about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
>> > work through it?  I had a few more questions in line.
>> >
>> > On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher <[hidden email]>
>> wrote:
>> >
>> >> 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.
>> >>
>> >>
>> > We don't usually expose the file name to people outside members, so I'm
>> not
>> > sure this would be useful.  Multiple dates are also not common.
>> >
>> >
>> >> The path to the source repository is missing completely.
>> >>
>> >
>> > Which source repository?  The podlings?  I have a prototype for gitbox
>> > podlings and think I can make it work for ASF git as well.  For SVN, we
>> can
>> > assume default or have a list of values.
>> >
>> >
>> >>
>> >> Some of these items could be transitory. For example distributionRights
>> >> may be confirmed but then something is added which negates those rights
>> >> until the issue is cleared up.
>> >>
>> >>
>> > +1
>> >
>> >
>> >> I wonder if it makes sense to provide links to email threads and/or Wiki
>> >> pages with the details?
>> >>
>> >> Regards,
>> >> Dave
>> >>
>> >> > On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]> wrote:
>> >> >
>> >> > What format of data is expected in the fields? Impala's new status
>> >> > page SVN config file
>> >> > <
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
>> >> >
>> >> > is:
>> >> >
>> >> > ---
>> >> > :issueTracker: jira
>> >> > :wiki: IMPALA
>> >> > :jira: IMPALA
>> >> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
>> >> > :asfCopyright:
>> >> > :distributionRights:
>> >> > :ipClearance:
>> >> > :sga:
>> >> > :website: http://impala.incubator.apache.org
>> >> > :graduationDate:
>> >> > :resolution:
>> >> >
>> >> > I do not know how to fill out asfCopyright, distributionRights,
>> >> > ipClearance, or sga. Note that I believe I understand what these
>> >> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
>> >> >
>> >> > I also don't know which one(s) correspond to the bold red "No Release
>> >> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
>> >> > has had a couple of ASF releases.
>> >> >
>> >> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <[hidden email]
>> >
>> >> wrote:
>> >> >> All,
>> >> >>
>> >> >> We're piloting a new format for the podling status pages.
>> Specifically,
>> >> >> the current status page leaves a lot to be desired - it's basically
>> >> crafted
>> >> >> html, there's no structure and its hard to find missing items.  The
>> end
>> >> >> goal is to have a web form editable in Whimsy, but until we get more
>> >> input
>> >> >> on what the content looks like I don't want to make changes like
>> that.
>> >> I'm
>> >> >> asking at this point for podlings to take a look at the status
>> output,
>> >> >> potentially update their own content, and see if they like the
>> output.
>> >> >>
>> >> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
>> >> (authentication
>> >> >> is via your ASF committer username/password) and find your podling,
>> >> you'll
>> >> >> see your current roster as well as your current status information.
>> >> >>
>> >> >> The status pages can be found in SVN at this directory
>> >> >>
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>> >> >>
>> >> >> Some more information can be found at
>> >> >>
>> >>
>> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
>> >> >>
>> >> >> If you're not sure what to fill out, feel free to reach out.
>> >> >>
>> >> >> John
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Sam Ruby
On Thu, Jun 15, 2017 at 1:21 PM, Jim Apple <[hidden email]> 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 need to delete the old structure; but we will soon get to the
point where there is tooling that depends on the new structure being
in place.  Let's create the new structure for old podlings, given that
(if history is any guide) there are podlings that exist now that won't
be graduating for many years.

I'd also suggest that we consider reconciling this with how we capture
data for PMCs (currently FOAF).  Anything that makes podlings be
modeled as much as possible like prototype PMCs is a good thing.

> 2. Provide a clear description of the meaning and formatting of each
> field in comments on the YAML file itself.

My recommendation is to treat the YAML file as internal state, and
focus instead of providing a usable web interface to manage the
internal state.

> 3. Provide guidance on how long it takes from SVN checkin to whimsy
> render change.

10 minutes.

> 4. Use git, not SVN

From an automation perspective, svn is preferred.  If we make the
normal way to update this data a web interface, svn is reasonable as
an exception mechanism, IMHO.

> 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.
>
> 6. Give the fields on the whimsy page names that correspond,
> one-to-one, with the YAML fields.
>
> 7. Give the Whimsy page headers more specific meanings. "Confirmation
> of ASF Copyright Headers on Source Code on" could mean confirmation by
> any number of people or committees. Which one is meant by this phrase?
> If it's the IPMC, and the first approved release is what is meant by
> this, change the name to "First Apache release" or something.
>
> 8. Provide the ability to lookup the information required to fill out
> the status page. How can a podling find out when the SGA was received?
> Please remember that podling personnel can change during incubation.

- Sam Ruby

> On Tue, Jun 13, 2017 at 6:04 PM, John D. Ament <[hidden email]> wrote:
>> Jim,
>>
>> For your specific cases, if all you want is to remove red text:
>>
>> - for :sga: enter the date in YYYY-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 as that's the day of the results of 2.8 which was the first
>> release to have no issues during review.
>>
>> But please do continue to provide input, want to make sure we're building
>> something useful, not a pain.
>>
>> HTH,
>>
>> John
>>
>> On Tue, Jun 13, 2017 at 8:52 PM Jim Apple <[hidden email]> wrote:
>>
>>> 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. Ament <[hidden email]>
>>> wrote:
>>> > 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 key (though I suppose this can be
>>> > multiple)
>>> > :proposal: link to the proposal page.
>>> > :asfCopyright: the date that we confirmed ASF copyright headers on the
>>> > source code (e.g. the first time a source release passed without any
>>> issues)
>>> > :distributionRights: the date that we confirmed the resulting binary
>>> > satisfied our release policies (e.g. the first time a release included a
>>> > binary without any issues)
>>> > :ipClearance: a link to the IP Clearance page for this podling.  I guess
>>> > this can be multiple?
>>> > :sga: date in which a SGA was received
>>> > :website: http://impala.incubator.apache.org
>>> > :graduationDate: to be filled in when the podling graduates
>>> > :resolution: tlp|subproject , if subproject the TLP should be in here
>>> > somehwere.  We may want to track as "sponsor."
>>> >
>>> > I can draft this up on a wiki page to gain more input.  What do you think
>>> > about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm to
>>> > work through it?  I had a few more questions in line.
>>> >
>>> > On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher <[hidden email]>
>>> wrote:
>>> >
>>> >> 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.
>>> >>
>>> >>
>>> > We don't usually expose the file name to people outside members, so I'm
>>> not
>>> > sure this would be useful.  Multiple dates are also not common.
>>> >
>>> >
>>> >> The path to the source repository is missing completely.
>>> >>
>>> >
>>> > Which source repository?  The podlings?  I have a prototype for gitbox
>>> > podlings and think I can make it work for ASF git as well.  For SVN, we
>>> can
>>> > assume default or have a list of values.
>>> >
>>> >
>>> >>
>>> >> Some of these items could be transitory. For example distributionRights
>>> >> may be confirmed but then something is added which negates those rights
>>> >> until the issue is cleared up.
>>> >>
>>> >>
>>> > +1
>>> >
>>> >
>>> >> I wonder if it makes sense to provide links to email threads and/or Wiki
>>> >> pages with the details?
>>> >>
>>> >> Regards,
>>> >> Dave
>>> >>
>>> >> > On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]> wrote:
>>> >> >
>>> >> > What format of data is expected in the fields? Impala's new status
>>> >> > page SVN config file
>>> >> > <
>>> >>
>>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
>>> >> >
>>> >> > is:
>>> >> >
>>> >> > ---
>>> >> > :issueTracker: jira
>>> >> > :wiki: IMPALA
>>> >> > :jira: IMPALA
>>> >> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
>>> >> > :asfCopyright:
>>> >> > :distributionRights:
>>> >> > :ipClearance:
>>> >> > :sga:
>>> >> > :website: http://impala.incubator.apache.org
>>> >> > :graduationDate:
>>> >> > :resolution:
>>> >> >
>>> >> > I do not know how to fill out asfCopyright, distributionRights,
>>> >> > ipClearance, or sga. Note that I believe I understand what these
>>> >> > things ARE, I just don't know how to word them -- "asfCopyright: OK"?
>>> >> >
>>> >> > I also don't know which one(s) correspond to the bold red "No Release
>>> >> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW, Impala
>>> >> > has had a couple of ASF releases.
>>> >> >
>>> >> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <[hidden email]
>>> >
>>> >> wrote:
>>> >> >> All,
>>> >> >>
>>> >> >> We're piloting a new format for the podling status pages.
>>> Specifically,
>>> >> >> the current status page leaves a lot to be desired - it's basically
>>> >> crafted
>>> >> >> html, there's no structure and its hard to find missing items.  The
>>> end
>>> >> >> goal is to have a web form editable in Whimsy, but until we get more
>>> >> input
>>> >> >> on what the content looks like I don't want to make changes like
>>> that.
>>> >> I'm
>>> >> >> asking at this point for podlings to take a look at the status
>>> output,
>>> >> >> potentially update their own content, and see if they like the
>>> output.
>>> >> >>
>>> >> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
>>> >> (authentication
>>> >> >> is via your ASF committer username/password) and find your podling,
>>> >> you'll
>>> >> >> see your current roster as well as your current status information.
>>> >> >>
>>> >> >> The status pages can be found in SVN at this directory
>>> >> >>
>>> >>
>>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
>>> >> >>
>>> >> >> Some more information can be found at
>>> >> >>
>>> >>
>>> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
>>> >> >>
>>> >> >> If you're not sure what to fill out, feel free to reach out.
>>> >> >>
>>> >> >> John
>>> >>
>>> >>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

John D. Ament-2
In reply to this post by Jim Apple
Jim,

Thanks for the input!

On Thu, Jun 15, 2017 at 1:22 PM Jim Apple <[hidden email]> 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.
>

So far, this is an experiment only.  No one is required to fill it out yet.


>
> 2. Provide a clear description of the meaning and formatting of each
> field in comments on the YAML file itself.
>

At some point, the yaml files will be there in spirit only and the actual
entry will be done via this screen.  There would need to be a read only
version available as well.


>
> 3. Provide guidance on how long it takes from SVN checkin to whimsy
> render change.
>
> 4. Use git, not SVN
>
> 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 interesting.  The ASF only releases source code.  However, the
second check is that your resulting binary is also compliant.


>
> 6. Give the fields on the whimsy page names that correspond,
> one-to-one, with the YAML fields.
>

It isn't 1:1, specifically, because some of the information is either/or in
nature.


>
> 7. Give the Whimsy page headers more specific meanings. "Confirmation
> of ASF Copyright Headers on Source Code on" could mean confirmation by
> any number of people or committees. Which one is meant by this phrase?
> If it's the IPMC, and the first approved release is what is meant by
> this, change the name to "First Apache release" or something.
>
>
Agreed.


> 8. Provide the ability to lookup the information required to fill out
> the status page. How can a podling find out when the SGA was received?
> Please remember that podling personnel can change during incubation.
>

True, but podlings should also have access to mail archives which includes
the SGA that was filed.  Worst case, ask your mentor, or even better, when
secretary receives it they set this value.


>
> On Tue, Jun 13, 2017 at 6:04 PM, John D. Ament <[hidden email]>
> wrote:
> > Jim,
> >
> > For your specific cases, if all you want is to remove red text:
> >
> > - for :sga: enter the date in YYYY-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 as that's the day of the results of 2.8 which was the first
> > release to have no issues during review.
> >
> > But please do continue to provide input, want to make sure we're building
> > something useful, not a pain.
> >
> > HTH,
> >
> > John
> >
> > On Tue, Jun 13, 2017 at 8:52 PM Jim Apple <[hidden email]> wrote:
> >
> >> 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. Ament <[hidden email]>
> >> wrote:
> >> > 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 key (though I suppose this can be
> >> > multiple)
> >> > :proposal: link to the proposal page.
> >> > :asfCopyright: the date that we confirmed ASF copyright headers on the
> >> > source code (e.g. the first time a source release passed without any
> >> issues)
> >> > :distributionRights: the date that we confirmed the resulting binary
> >> > satisfied our release policies (e.g. the first time a release
> included a
> >> > binary without any issues)
> >> > :ipClearance: a link to the IP Clearance page for this podling.  I
> guess
> >> > this can be multiple?
> >> > :sga: date in which a SGA was received
> >> > :website: http://impala.incubator.apache.org
> >> > :graduationDate: to be filled in when the podling graduates
> >> > :resolution: tlp|subproject , if subproject the TLP should be in here
> >> > somehwere.  We may want to track as "sponsor."
> >> >
> >> > I can draft this up on a wiki page to gain more input.  What do you
> think
> >> > about using https://wiki.apache.org/incubator/PodlingStatusBrainstorm
> to
> >> > work through it?  I had a few more questions in line.
> >> >
> >> > On Tue, Jun 13, 2017 at 7:09 PM Dave Fisher <[hidden email]>
> >> wrote:
> >> >
> >> >> 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.
> >> >>
> >> >>
> >> > We don't usually expose the file name to people outside members, so
> I'm
> >> not
> >> > sure this would be useful.  Multiple dates are also not common.
> >> >
> >> >
> >> >> The path to the source repository is missing completely.
> >> >>
> >> >
> >> > Which source repository?  The podlings?  I have a prototype for gitbox
> >> > podlings and think I can make it work for ASF git as well.  For SVN,
> we
> >> can
> >> > assume default or have a list of values.
> >> >
> >> >
> >> >>
> >> >> Some of these items could be transitory. For example
> distributionRights
> >> >> may be confirmed but then something is added which negates those
> rights
> >> >> until the issue is cleared up.
> >> >>
> >> >>
> >> > +1
> >> >
> >> >
> >> >> I wonder if it makes sense to provide links to email threads and/or
> Wiki
> >> >> pages with the details?
> >> >>
> >> >> Regards,
> >> >> Dave
> >> >>
> >> >> > On Jun 13, 2017, at 8:22 AM, Jim Apple <[hidden email]>
> wrote:
> >> >> >
> >> >> > What format of data is expected in the fields? Impala's new status
> >> >> > page SVN config file
> >> >> > <
> >> >>
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/impala.yml
> >> >> >
> >> >> > is:
> >> >> >
> >> >> > ---
> >> >> > :issueTracker: jira
> >> >> > :wiki: IMPALA
> >> >> > :jira: IMPALA
> >> >> > :proposal: http://wiki.apache.org/incubator/ImpalaProposal
> >> >> > :asfCopyright:
> >> >> > :distributionRights:
> >> >> > :ipClearance:
> >> >> > :sga:
> >> >> > :website: http://impala.incubator.apache.org
> >> >> > :graduationDate:
> >> >> > :resolution:
> >> >> >
> >> >> > I do not know how to fill out asfCopyright, distributionRights,
> >> >> > ipClearance, or sga. Note that I believe I understand what these
> >> >> > things ARE, I just don't know how to word them -- "asfCopyright:
> OK"?
> >> >> >
> >> >> > I also don't know which one(s) correspond to the bold red "No
> Release
> >> >> > Yet" on <https://whimsy.apache.org/roster/ppmc/impala>. FWIW,
> Impala
> >> >> > has had a couple of ASF releases.
> >> >> >
> >> >> > On Mon, Jun 12, 2017 at 6:02 PM, John D. Ament <
> [hidden email]
> >> >
> >> >> wrote:
> >> >> >> All,
> >> >> >>
> >> >> >> We're piloting a new format for the podling status pages.
> >> Specifically,
> >> >> >> the current status page leaves a lot to be desired - it's
> basically
> >> >> crafted
> >> >> >> html, there's no structure and its hard to find missing items.
> The
> >> end
> >> >> >> goal is to have a web form editable in Whimsy, but until we get
> more
> >> >> input
> >> >> >> on what the content looks like I don't want to make changes like
> >> that.
> >> >> I'm
> >> >> >> asking at this point for podlings to take a look at the status
> >> output,
> >> >> >> potentially update their own content, and see if they like the
> >> output.
> >> >> >>
> >> >> >> If you navigate to https://whimsy.apache.org/roster/ppmc/
> >> >> (authentication
> >> >> >> is via your ASF committer username/password) and find your
> podling,
> >> >> you'll
> >> >> >> see your current roster as well as your current status
> information.
> >> >> >>
> >> >> >> The status pages can be found in SVN at this directory
> >> >> >>
> >> >>
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/
> >> >> >>
> >> >> >> Some more information can be found at
> >> >> >>
> >> >>
> >>
> https://lists.apache.org/thread.html/9504139b5ee9880fdb278f86757803c711fbc962e1934ef2c01a8ed0@%3Cgeneral.incubator.apache.org%3E
> >> >> >>
> >> >> >> If you're not sure what to fill out, feel free to reach out.
> >> >> >>
> >> >> >> John
> >> >>
> >> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

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 interesting.  The ASF only releases source code.  However, the
> second check is that your resulting binary is also compliant.

The "your resulting binary" is for projects that distribute
convenience binaries?

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

John D. Ament-2
On Thu, Jun 15, 2017 at 3:50 PM Jim Apple <[hidden email]> 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 non-source-tarball release
> >> artefact, it's not meaningful for Impala.
> >>
> >
> > Hmm that's interesting.  The ASF only releases source code.  However, the
> > second check is that your resulting binary is also compliant.
>
> The "your resulting binary" is for projects that distribute
> convenience binaries?
>

No - but either way Impala is probably in the clear.

The resulting binary is an issue if:

- You use statically linked libraries (e.g. they get embedded in the binary)
- You do provide a distribution style binary that includes them in the
package (e.g. a rpm or deb or tar or zip)

As an example, ActiveMQ Artemis depends on an optional extension for
libaio.  libaio is LGPL licensed.  This binary is OK because it is
optional, the user has to do something to enable it.  But do note they ship
it as a convenience.


>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Loading...