Re: DOAP futures (ASF project metadata)

[Dave Fisher]

Hi -

> On Mar 6, 2019, at 4:51 AM, Shane Curcuru  wrote:
> 
> Bertrand Delacretaz wrote on 3/5/19 7:23 AM:
>> Hi,
>> 
>> On Tue, Mar 5, 2019 at 1:16 PM Mark Cox  wrote:
>>> ... So before investing too more time into this, I wanted to find out if
>>> there's been any real attempt or plan or investigation to replace the DOAP
>>> files within ASF with something else
> ...snip...
>> It might take some initial effort to consolidate that data and fix the
>> software that uses it but I think it's well worth it. Considering that
>> this is infrastructure related, we might ask for funding for this
>> initial cleanup task as I'm not sure we'll get there with volunteer
>> energy only.
> 
> Indeed, centralizing project (including podling) metadata - somehow! -
> is a real need that we've never been able to meet.  I also support
> finding funding for this to task infra to work on it (which is a topic
> for other lists, but it's important to note it here).

I’m currently working on the podling clutch related metadata from ground truth.

Podlings.xml is a key part of this and is currently hand edited. An editing 
error this morning caused Whimsy roster pages to fail. I was able to fix this 
quickly and the new podling caused new error states in the incubator clutch 
process which I fixed.

My goal with the clutch is multiple.

(1) Improve Incubator workflows to better inform podling’s about their state 
wrt graduating to become an Apache TLP.

(2) Improve the process so that all incubator state is found in the ground 
truth and from adaptation to a decade old reporting structure. For example of 
the 51 podlings last week. 50 use gitbox yet Git was not really accommodated. 
Gitbox.apache.org/repositories.json provides ground truth on all Apache git 
repositories.

I would certainly like to be involved …

Regards,
Dave

> 
> Key design criteria:
> 
> - Easy to maintain the whole system.
> 
> - Easy to consume for all users - whimsy especially (since other places
> rely on that), the www.a.o website, *plus* external consumers who might
> want to scrape our project universe.
> 
> - Easy for projects to update.  In particular, having Maven,
> Cocoon/Forrest, GitHub plugins to auto-generate needed data is key; we
> can't ask all projects with existing widely-used tooling to have to add
> unusual steps to their release processes.

As much data as possible should be found in the state of our systems.
For example we should be able to create a download json for a release by 
examining the svn for dist.apache.org .

> 
> Presuming board/ops/infra make this a real project (i.e. funding and
> timeline), where should the design discussion happen?

Regards,
Dave
> 
> -- 
> 
> - Shane
>  Director & Member
>  The Apache Software Foundation
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 

Google Summer of Code 2019 Mentor Registration

[Ulrich Stärk]

Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted 
organizations for
Google Summer of Code 2019! [1,2]

It is now time for mentors to sign up, so please pass this email on to your 
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org you 
should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and PMC 
acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor 
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will use 
the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to ensure 
the mentor is in good
standing with the community. When you receive a request for acknowledgement, 
please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see previous 
emails for details).
Students will now begin to explore ideas so if you haven’t already done so, 
record your ideas
immediately!

Cheers,

The Apache GSoC Team

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2019 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code 2018 
projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/6614885824200704/
[3] https://summerofcode.withgoogle.com/

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org