Contents of Podling Status Tracking

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Contents of Podling Status Tracking

John D. Ament-2
As a follow up to my prior question, (
https://lists.apache.org/thread.html/31119aafbc4260720d222666f3efd01f2fe2975e424039ea539c9cb6@%3Cgeneral.incubator.apache.org%3E
).
Looking at our current tracking file for podlings, I wonder how much of the
information is useful.  Let's use Traffic Control as a for instance here:
http://incubator.apache.org/projects/trafficcontrol.html (its nothing
they're doing bad, I just happened to grab them)

- The committer list is fully replaced by the Whimsy Roster Tool
- Do we care about News? Shouldn't this be captured in the quarterly
reports?
- I see a lot of usefulness in tracking the Podling Name Search request
- The first few questions have to do with the actual vote.  I think these
can best be captured by two fields - "Sponsor" and "Date Accepted into
Incubator"
- Infra section - I think all of these are important, we may want to expand
some of the options to include gitbox and other tools that are managed
outside our hosted infrastructure.
- Mentor section - I'm not sure how useful this is, but I want to get
others opinions.  Mentors being on the IPMC is a pre-req for votes, so this
is hopefully less of an issue.
- Copyright - I believe this can be replaced by a single field "Date SGA
Received".  Copyright headers are subjective.
- Add a new field "Date of IP Clearance" for projects using IP Clearance
instead of SGA (e.g. already Apache v2)
- Verify Distribution Rights - I think this can be rewritten to instead say
"Date of Release with no Source Licensing Issues" (listing out the bullet
points mentioned here) and a new field "Date of Release with no Binary
Licensing Issues" (indicating some of the Cat-B/Optional Cat-X stuff)
- I don't think we need the committers section at the bottom, since the
roster would be controlled from Whimsy itself.

Is there more information that we could leverage to make this easier to
watch?  I figure that once a podling has filled out all of these (except
for one of SGA/IP Clearance) we can tell them they're close to graduation.

John
Reply | Threaded
Open this post in threaded view
|

Re: Contents of Podling Status Tracking

sebb-2-2
On 6 June 2017 at 04:22, John D. Ament <[hidden email]> wrote:
> As a follow up to my prior question, (
> https://lists.apache.org/thread.html/31119aafbc4260720d222666f3efd01f2fe2975e424039ea539c9cb6@%3Cgeneral.incubator.apache.org%3E
> ).
> Looking at our current tracking file for podlings, I wonder how much of the
> information is useful.  Let's use Traffic Control as a for instance here:
> http://incubator.apache.org/projects/trafficcontrol.html (its nothing
> they're doing bad, I just happened to grab them)

However their status file does not contain the full range of data that
is normally present.
e.g. no website link, no repo link, no champion/mentors

> - The committer list is fully replaced by the Whimsy Roster Tool
> - Do we care about News? Shouldn't this be captured in the quarterly
> reports?

It's easier for outsiders to read here.
It perhaps encourages the podling to think about progress.

> - I see a lot of usefulness in tracking the Podling Name Search request
> - The first few questions have to do with the actual vote.  I think these
> can best be captured by two fields - "Sponsor" and "Date Accepted into
> Incubator"
> - Infra section - I think all of these are important, we may want to expand
> some of the options to include gitbox and other tools that are managed
> outside our hosted infrastructure.
> - Mentor section - I'm not sure how useful this is, but I want to get
> others opinions.  Mentors being on the IPMC is a pre-req for votes, so this
> is hopefully less of an issue.
> - Copyright - I believe this can be replaced by a single field "Date SGA
> Received".  Copyright headers are subjective.
> - Add a new field "Date of IP Clearance" for projects using IP Clearance
> instead of SGA (e.g. already Apache v2)
> - Verify Distribution Rights - I think this can be rewritten to instead say
> "Date of Release with no Source Licensing Issues" (listing out the bullet
> points mentioned here) and a new field "Date of Release with no Binary
> Licensing Issues" (indicating some of the Cat-B/Optional Cat-X stuff)
> - I don't think we need the committers section at the bottom, since the
> roster would be controlled from Whimsy itself.
>
> Is there more information that we could leverage to make this easier to
> watch?  I figure that once a podling has filled out all of these (except
> for one of SGA/IP Clearance) we can tell them they're close to graduation.

I find the status files useful for quickly finding information about a
project that would otherwise require a trawl of lots of pages of the
website.
It also allows the PPMC to record info about the project (e.g. git
repo, JIRA etc) before the website has been set up.

It is useful beyond just tracking progress to graduation/retirement.

Having a single page to show summary info and track the status is
something I think we should keep.
But I agree it needs to be easier to maintain and it should be obvious
when bits of information are missing.

This would be easier to do if the page were generated from properly
structured data files.

Could the data all be handled in podlings.xml?
Or should podlings.xml be split into individual files?

> John

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

Reply | Threaded
Open this post in threaded view
|

Re: Contents of Podling Status Tracking

John D. Ament-2
On Tue, Jun 6, 2017 at 6:40 AM sebb <[hidden email]> wrote:

> On 6 June 2017 at 04:22, John D. Ament <[hidden email]> wrote:
> > As a follow up to my prior question, (
> >
> https://lists.apache.org/thread.html/31119aafbc4260720d222666f3efd01f2fe2975e424039ea539c9cb6@%3Cgeneral.incubator.apache.org%3E
> > ).
> > Looking at our current tracking file for podlings, I wonder how much of
> the
> > information is useful.  Let's use Traffic Control as a for instance here:
> > http://incubator.apache.org/projects/trafficcontrol.html (its nothing
> > they're doing bad, I just happened to grab them)
>
> However their status file does not contain the full range of data that
> is normally present.
> e.g. no website link, no repo link, no champion/mentors
>


Good points.  I think we definitely want to have areas for source repos,
the website (override-able?), confluence keys, etc.

As mentioned, I'm less concerned about roster information at this point on
the status page because of Whimsy.


> > - The committer list is fully replaced by the Whimsy Roster Tool
> > - Do we care about News? Shouldn't this be captured in the quarterly
> > reports?
>
> It's easier for outsiders to read here.
> It perhaps encourages the podling to think about progress.
>
>
So maybe a free form area for news items?


> > - I see a lot of usefulness in tracking the Podling Name Search request
> > - The first few questions have to do with the actual vote.  I think these
> > can best be captured by two fields - "Sponsor" and "Date Accepted into
> > Incubator"
> > - Infra section - I think all of these are important, we may want to
> expand
> > some of the options to include gitbox and other tools that are managed
> > outside our hosted infrastructure.
> > - Mentor section - I'm not sure how useful this is, but I want to get
> > others opinions.  Mentors being on the IPMC is a pre-req for votes, so
> this
> > is hopefully less of an issue.
> > - Copyright - I believe this can be replaced by a single field "Date SGA
> > Received".  Copyright headers are subjective.
> > - Add a new field "Date of IP Clearance" for projects using IP Clearance
> > instead of SGA (e.g. already Apache v2)
> > - Verify Distribution Rights - I think this can be rewritten to instead
> say
> > "Date of Release with no Source Licensing Issues" (listing out the bullet
> > points mentioned here) and a new field "Date of Release with no Binary
> > Licensing Issues" (indicating some of the Cat-B/Optional Cat-X stuff)
> > - I don't think we need the committers section at the bottom, since the
> > roster would be controlled from Whimsy itself.
> >
> > Is there more information that we could leverage to make this easier to
> > watch?  I figure that once a podling has filled out all of these (except
> > for one of SGA/IP Clearance) we can tell them they're close to
> graduation.
>
> I find the status files useful for quickly finding information about a
> project that would otherwise require a trawl of lots of pages of the
> website.
> It also allows the PPMC to record info about the project (e.g. git
> repo, JIRA etc) before the website has been set up.
>


I've been going back and forth on this.  I think you're thinking along my
lines - should the status file be public or private.  I think we need a
public read only version of the status, in addition to the writeable
version.


>
> It is useful beyond just tracking progress to graduation/retirement.
>
> Having a single page to show summary info and track the status is
> something I think we should keep.
> But I agree it needs to be easier to maintain and it should be obvious
> when bits of information are missing.
>
>
Huge +1.  My biggest issue is that it's arbitrary HTML.  Any podling can
add stuff as they see fit, or remove sections, and it's not obvious.


> This would be easier to do if the page were generated from properly
> structured data files.
>
> Could the data all be handled in podlings.xml?
> Or should podlings.xml be split into individual files?
>

I feel like splitting is more desirable.  From what I'm seeing, it's adding
20 new data elements.  Merging podlings.xml + the status file into a new
file makes a bit more sense.  JSON is easier to parse, but leaves more to
be desired from someone manually tweaking the file.


>
> > John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Contents of Podling Status Tracking

Bertrand Delacretaz
In reply to this post by John D. Ament-2
Hi,

On Tue, Jun 6, 2017 at 5:22 AM, John D. Ament <[hidden email]> wrote:
> ...Looking at our current tracking file for podlings, I wonder how much of the
> information is useful...

I agree that a good part of the information found in podling status
pages belongs on their own websites, as soon as those are up.

Note that http://incubator.apache.org/clutch.html does scrape some
data from those pages AFAIK, so it might break if we remove things.

It looks to me like podlings.xml + whimsy roster + a graduation
checklist / report including items like software grants, list of
releases, podling name search etc. would do - but I haven't checked
the impact on the clutch report.

That graduation report (along with the optional maturity model
self-assessment) can then live on the podling's website to gradually
evolve during incubation, and be sumitted along with the graduation
request. There's no need to check those things beforehand, IMO, as
long as podlings have a template for that report which indicates
what's required.

-Bertrand

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

Reply | Threaded
Open this post in threaded view
|

Re: Contents of Podling Status Tracking

John D. Ament-2
On Tue, Jun 6, 2017 at 7:32 AM Bertrand Delacretaz <
[hidden email]> wrote:

> Hi,
>
> On Tue, Jun 6, 2017 at 5:22 AM, John D. Ament <[hidden email]>
> wrote:
> > ...Looking at our current tracking file for podlings, I wonder how much
> of the
> > information is useful...
>
> I agree that a good part of the information found in podling status
> pages belongs on their own websites, as soon as those are up.
>
> Note that http://incubator.apache.org/clutch.html does scrape some
> data from those pages AFAIK, so it might break if we remove things.
>
>
I'm not sure how much others care about clutch.  It was never updated to
handle things like git, github, etc.  I think if the remaining useful data
from clutch can be folded in to the public display we're OK.

I do think some of the automated information it provides is useful - number
of days incubating, distribution area, but I'm personally OK if clutch goes
away when this is all done (work has started to generate podling reporting
data out of whimsy using a data feed,
https://whimsy.apache.org/public/public_podlings.json  - take a look at the
schedule section).  I never quite liked the color coded table with
characters for column headers.

If we still want an incubator level "executive summary" type of report,
that can be built from the data feed as well.


> It looks to me like podlings.xml + whimsy roster + a graduation
> checklist / report including items like software grants, list of
> releases, podling name search etc. would do - but I haven't checked
> the impact on the clutch report.
>

Funny thing.  I've never actually been on the creating side for an
incubator release.  Does projects.a.o work for podlings?  I do see one of
my podlings there, and if we can pull that data we can show release data as
well automatically.


>
> That graduation report (along with the optional maturity model
> self-assessment) can then live on the podling's website to gradually
> evolve during incubation, and be sumitted along with the graduation
> request. There's no need to check those things beforehand, IMO, as
> long as podlings have a template for that report which indicates
> what's required.
>
>
I think if a podling isn't sure if they're ready to graduate, having
someone look at this list would be useful.


> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Contents of Podling Status Tracking

Sam Ruby
In reply to this post by John D. Ament-2
Not sure where to comment, so I'll top post.

Some of the data that you mentioned doesn't need to be in the status
file as it can be generated from other sources.  For example:
https://whimsy.apache.org/board/agenda/json/podlingnamesearch.  I'll
refactor that code and add that information to the ppmc pages of the
roster tool.

YAML is more human editable than JSON.  As Sebb points out elsewhere,
it also supports comments.

One thing that whimsy should do is spit out a digested and accumulated
set of information in JSON which can be read by other tools.  A good
place for a public view would be the phonebook application.

I see as I typed this Bertrand brought up clutch and graduation
checklist.  I see those as items that can be incorporated into the
roster tool, with the added value that this tool is both read/write.
See something that needs to be changed?  Given the right permissions,
you can fix it right there, and interested parties will be notified of
the change.

I've already added a button to the bottom of the PPMC roster pages to
help you draft a graduation resolution.  At the moment, it doesn't do
anything more than display the resolution which you can copy/paste.
This not only will save a few minutes, the resolution will contain the
correct names and ids.

- Sam Ruby

On Tue, Jun 6, 2017 at 7:11 AM, John D. Ament <[hidden email]> wrote:

> On Tue, Jun 6, 2017 at 6:40 AM sebb <[hidden email]> wrote:
>
>> On 6 June 2017 at 04:22, John D. Ament <[hidden email]> wrote:
>> > As a follow up to my prior question, (
>> >
>> https://lists.apache.org/thread.html/31119aafbc4260720d222666f3efd01f2fe2975e424039ea539c9cb6@%3Cgeneral.incubator.apache.org%3E
>> > ).
>> > Looking at our current tracking file for podlings, I wonder how much of
>> the
>> > information is useful.  Let's use Traffic Control as a for instance here:
>> > http://incubator.apache.org/projects/trafficcontrol.html (its nothing
>> > they're doing bad, I just happened to grab them)
>>
>> However their status file does not contain the full range of data that
>> is normally present.
>> e.g. no website link, no repo link, no champion/mentors
>>
>
>
> Good points.  I think we definitely want to have areas for source repos,
> the website (override-able?), confluence keys, etc.
>
> As mentioned, I'm less concerned about roster information at this point on
> the status page because of Whimsy.
>
>
>> > - The committer list is fully replaced by the Whimsy Roster Tool
>> > - Do we care about News? Shouldn't this be captured in the quarterly
>> > reports?
>>
>> It's easier for outsiders to read here.
>> It perhaps encourages the podling to think about progress.
>>
>>
> So maybe a free form area for news items?
>
>
>> > - I see a lot of usefulness in tracking the Podling Name Search request
>> > - The first few questions have to do with the actual vote.  I think these
>> > can best be captured by two fields - "Sponsor" and "Date Accepted into
>> > Incubator"
>> > - Infra section - I think all of these are important, we may want to
>> expand
>> > some of the options to include gitbox and other tools that are managed
>> > outside our hosted infrastructure.
>> > - Mentor section - I'm not sure how useful this is, but I want to get
>> > others opinions.  Mentors being on the IPMC is a pre-req for votes, so
>> this
>> > is hopefully less of an issue.
>> > - Copyright - I believe this can be replaced by a single field "Date SGA
>> > Received".  Copyright headers are subjective.
>> > - Add a new field "Date of IP Clearance" for projects using IP Clearance
>> > instead of SGA (e.g. already Apache v2)
>> > - Verify Distribution Rights - I think this can be rewritten to instead
>> say
>> > "Date of Release with no Source Licensing Issues" (listing out the bullet
>> > points mentioned here) and a new field "Date of Release with no Binary
>> > Licensing Issues" (indicating some of the Cat-B/Optional Cat-X stuff)
>> > - I don't think we need the committers section at the bottom, since the
>> > roster would be controlled from Whimsy itself.
>> >
>> > Is there more information that we could leverage to make this easier to
>> > watch?  I figure that once a podling has filled out all of these (except
>> > for one of SGA/IP Clearance) we can tell them they're close to
>> graduation.
>>
>> I find the status files useful for quickly finding information about a
>> project that would otherwise require a trawl of lots of pages of the
>> website.
>> It also allows the PPMC to record info about the project (e.g. git
>> repo, JIRA etc) before the website has been set up.
>>
>
>
> I've been going back and forth on this.  I think you're thinking along my
> lines - should the status file be public or private.  I think we need a
> public read only version of the status, in addition to the writeable
> version.
>
>
>>
>> It is useful beyond just tracking progress to graduation/retirement.
>>
>> Having a single page to show summary info and track the status is
>> something I think we should keep.
>> But I agree it needs to be easier to maintain and it should be obvious
>> when bits of information are missing.
>>
>>
> Huge +1.  My biggest issue is that it's arbitrary HTML.  Any podling can
> add stuff as they see fit, or remove sections, and it's not obvious.
>
>
>> This would be easier to do if the page were generated from properly
>> structured data files.
>>
>> Could the data all be handled in podlings.xml?
>> Or should podlings.xml be split into individual files?
>>
>
> I feel like splitting is more desirable.  From what I'm seeing, it's adding
> 20 new data elements.  Merging podlings.xml + the status file into a new
> file makes a bit more sense.  JSON is easier to parse, but leaves more to
> be desired from someone manually tweaking the file.
>
>
>>
>> > 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
|

Re: Contents of Podling Status Tracking

John D. Ament-2
On Tue, Jun 6, 2017 at 7:44 AM Sam Ruby <[hidden email]> wrote:

> Not sure where to comment, so I'll top post.
>
> Some of the data that you mentioned doesn't need to be in the status
> file as it can be generated from other sources.  For example:
> https://whimsy.apache.org/board/agenda/json/podlingnamesearch.  I'll
> refactor that code and add that information to the ppmc pages of the
> roster tool.
>

I don't see the code that generates this.  Where did it come from?


>
> YAML is more human editable than JSON.  As Sebb points out elsewhere,
> it also supports comments.
>
> One thing that whimsy should do is spit out a digested and accumulated
> set of information in JSON which can be read by other tools.  A good
> place for a public view would be the phonebook application.
>

Agreed.  All of the changes I have locally are going into
public_podlings.json first.  Once that works, we can start to incorporate
into other pages.


>
> I see as I typed this Bertrand brought up clutch and graduation
> checklist.  I see those as items that can be incorporated into the
> roster tool, with the added value that this tool is both read/write.
> See something that needs to be changed?  Given the right permissions,
> you can fix it right there, and interested parties will be notified of
> the change.
>
> I've already added a button to the bottom of the PPMC roster pages to
> help you draft a graduation resolution.  At the moment, it doesn't do
> anything more than display the resolution which you can copy/paste.
> This not only will save a few minutes, the resolution will contain the
> correct names and ids.
>

I gave it a field run, it looks nice.


>
> - Sam Ruby
>
> On Tue, Jun 6, 2017 at 7:11 AM, John D. Ament <[hidden email]>
> wrote:
> > On Tue, Jun 6, 2017 at 6:40 AM sebb <[hidden email]> wrote:
> >
> >> On 6 June 2017 at 04:22, John D. Ament <[hidden email]> wrote:
> >> > As a follow up to my prior question, (
> >> >
> >>
> https://lists.apache.org/thread.html/31119aafbc4260720d222666f3efd01f2fe2975e424039ea539c9cb6@%3Cgeneral.incubator.apache.org%3E
> >> > ).
> >> > Looking at our current tracking file for podlings, I wonder how much
> of
> >> the
> >> > information is useful.  Let's use Traffic Control as a for instance
> here:
> >> > http://incubator.apache.org/projects/trafficcontrol.html (its nothing
> >> > they're doing bad, I just happened to grab them)
> >>
> >> However their status file does not contain the full range of data that
> >> is normally present.
> >> e.g. no website link, no repo link, no champion/mentors
> >>
> >
> >
> > Good points.  I think we definitely want to have areas for source repos,
> > the website (override-able?), confluence keys, etc.
> >
> > As mentioned, I'm less concerned about roster information at this point
> on
> > the status page because of Whimsy.
> >
> >
> >> > - The committer list is fully replaced by the Whimsy Roster Tool
> >> > - Do we care about News? Shouldn't this be captured in the quarterly
> >> > reports?
> >>
> >> It's easier for outsiders to read here.
> >> It perhaps encourages the podling to think about progress.
> >>
> >>
> > So maybe a free form area for news items?
> >
> >
> >> > - I see a lot of usefulness in tracking the Podling Name Search
> request
> >> > - The first few questions have to do with the actual vote.  I think
> these
> >> > can best be captured by two fields - "Sponsor" and "Date Accepted into
> >> > Incubator"
> >> > - Infra section - I think all of these are important, we may want to
> >> expand
> >> > some of the options to include gitbox and other tools that are managed
> >> > outside our hosted infrastructure.
> >> > - Mentor section - I'm not sure how useful this is, but I want to get
> >> > others opinions.  Mentors being on the IPMC is a pre-req for votes, so
> >> this
> >> > is hopefully less of an issue.
> >> > - Copyright - I believe this can be replaced by a single field "Date
> SGA
> >> > Received".  Copyright headers are subjective.
> >> > - Add a new field "Date of IP Clearance" for projects using IP
> Clearance
> >> > instead of SGA (e.g. already Apache v2)
> >> > - Verify Distribution Rights - I think this can be rewritten to
> instead
> >> say
> >> > "Date of Release with no Source Licensing Issues" (listing out the
> bullet
> >> > points mentioned here) and a new field "Date of Release with no Binary
> >> > Licensing Issues" (indicating some of the Cat-B/Optional Cat-X stuff)
> >> > - I don't think we need the committers section at the bottom, since
> the
> >> > roster would be controlled from Whimsy itself.
> >> >
> >> > Is there more information that we could leverage to make this easier
> to
> >> > watch?  I figure that once a podling has filled out all of these
> (except
> >> > for one of SGA/IP Clearance) we can tell them they're close to
> >> graduation.
> >>
> >> I find the status files useful for quickly finding information about a
> >> project that would otherwise require a trawl of lots of pages of the
> >> website.
> >> It also allows the PPMC to record info about the project (e.g. git
> >> repo, JIRA etc) before the website has been set up.
> >>
> >
> >
> > I've been going back and forth on this.  I think you're thinking along my
> > lines - should the status file be public or private.  I think we need a
> > public read only version of the status, in addition to the writeable
> > version.
> >
> >
> >>
> >> It is useful beyond just tracking progress to graduation/retirement.
> >>
> >> Having a single page to show summary info and track the status is
> >> something I think we should keep.
> >> But I agree it needs to be easier to maintain and it should be obvious
> >> when bits of information are missing.
> >>
> >>
> > Huge +1.  My biggest issue is that it's arbitrary HTML.  Any podling can
> > add stuff as they see fit, or remove sections, and it's not obvious.
> >
> >
> >> This would be easier to do if the page were generated from properly
> >> structured data files.
> >>
> >> Could the data all be handled in podlings.xml?
> >> Or should podlings.xml be split into individual files?
> >>
> >
> > I feel like splitting is more desirable.  From what I'm seeing, it's
> adding
> > 20 new data elements.  Merging podlings.xml + the status file into a new
> > file makes a bit more sense.  JSON is easier to parse, but leaves more to
> > be desired from someone manually tweaking the file.
> >
> >
> >>
> >> > 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
|

Re: Contents of Podling Status Tracking

Bertrand Delacretaz
In reply to this post by John D. Ament-2
On Tue, Jun 6, 2017 at 1:43 PM, John D. Ament <[hidden email]> wrote:
> ...I'm not sure how much others care about clutch....

> ...work has started to generate podling reporting
> data out of whimsy using a data feed,
> https://whimsy.apache.org/public/public_podlings.json  - take a look at the
> schedule section...

ok, it looks like that data would be sufficient if clutch is phased out.

I'm fine with removing Clutch as long as that's a conscious decision,
especially if things are available in Whimsy backed by structured text
files.

-Bertrand

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

Reply | Threaded
Open this post in threaded view
|

Re: Contents of Podling Status Tracking

Sam Ruby
In reply to this post by John D. Ament-2
On Tue, Jun 6, 2017 at 7:49 AM, John D. Ament <[hidden email]> wrote:
> On Tue, Jun 6, 2017 at 7:44 AM Sam Ruby <[hidden email]> wrote:
>>
>> Some of the data that you mentioned doesn't need to be in the status
>> file as it can be generated from other sources.  For example:
>> https://whimsy.apache.org/board/agenda/json/podlingnamesearch.  I'll
>> refactor that code and add that information to the ppmc pages of the
>> roster tool.
>
> I don't see the code that generates this.  Where did it come from?

Here's the code:

https://github.com/apache/whimsy/blob/6752628340f330303089fd7521724381f653ca97/www/board/agenda/routes.rb#L186

The parsing logic will move to
https://github.com/apache/whimsy/blob/master/lib/whimsy/asf/podlings.rb,
and therefore be usable by multiple tools (in this case, the board
agenda and roster tools).

>> YAML is more human editable than JSON.  As Sebb points out elsewhere,
>> it also supports comments.
>>
>> One thing that whimsy should do is spit out a digested and accumulated
>> set of information in JSON which can be read by other tools.  A good
>> place for a public view would be the phonebook application.
>>
>
> Agreed.  All of the changes I have locally are going into
> public_podlings.json first.  Once that works, we can start to incorporate
> into other pages.

Recommendation: add any logic to
https://github.com/apache/whimsy/blob/master/lib/whimsy/asf/podlings.rb
and similar pages, have the existing cron job that extracts that data
merely fetch it from the library.  The library can then be used by the
roster tool.

- Sam Ruby

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

Reply | Threaded
Open this post in threaded view
|

Re: Contents of Podling Status Tracking

Sam Ruby
In reply to this post by Sam Ruby
On Tue, Jun 6, 2017 at 7:43 AM, Sam Ruby <[hidden email]> wrote:
>
> YAML is more human editable than JSON.  As Sebb points out elsewhere,
> it also supports comments.

Alternative: create DOAP files for podlings.  In general, model
podlings like PMCs as much and as soon as possible.

- Sam Ruby

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