The best place to start this discussion in terms of needs is over on the
dev@community mailing list - no need to include folks individually
unless they ask.

There are several different issues to work on:

- Need and design: what does the ASF or some projects actually need, and
how could we better present a design that would be easier to use and
maintain?  Note also that projects use a wide variety of site generation
and maintenance tools, and to get better adoption any new tool needs to
fit easily into existing Forrest, Maven, or other tools that various
projects use (i.e., adoption on a per-project level, like for
project.a.o/mailinglist pages, would be up to each project)

- Work: Who is actually going to provide the code, take feedback from
various parties, and help maintain any new solution?  This is where
having an iterative design is important, because many of these efforts
start with great new volunteers, but never get finished or fully
deployed when the rest of the world interferes with people's dayjobs.

- Code: Any apache.org hosted solution needs to be maintained by the
infra team.  In particular, infra is moving to centralize all the
per-person data into our custom LDAP scheme, which is being expanded to
include PMC membership and plenty of other data.  Some info is on the blog:

  https://blogs.apache.org/infra/tags/ldap
  https://id.apache.org/

There's been a lot of updates to how the core LDAP is being used and is
exposed on http or https endpoints in the past year, so it would be
useful to get a better overview of what the core people/projects data is
available already.

- Shane

On 10/13/14 9:19 AM, Pierre Smits wrote:
> Hi Gabriella,
> 
> I have been pondering a bit on how Apache OFBiz could support The ASF as
> the unified front end regarding:
> 
>   * subscribing to and unsubscribing from mailing lists of projects and
>     offices
>   * profiling the Projects, Corporate Officers, ASF Members, Vice
>     Presidents, PMC Members, Committers, Contributors and Offices
>   * the invitation processes regarding new ASF Members, PMC Members and
>     Committers
>   * the 'Change of Guard' process regarding Board Members, Office and
>     Project VPs
> 
> Based on some demo data I have mocked up how this could look like and
> have created a Powerpoint to show and explain this a bit.
> In the attached PDF you can get a feel of some screenshots. In the notes
> of each slide you'll find a short description. 
> 
> If you would like to investigate and/or pursue the possibilities
> further, feel free to contact me to exchange ideas, viewpoints, etc. If
> you have trouble accessing the attached file please send me a note.
> 
> Best Regards,
> 
> 
> Pierre Smits
> 
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com <http://www.orrtiz.com/>
> 
> On Fri, Oct 3, 2014 at 2:42 PM, Gabriela Gibson
> <gabriela.gib...@gmail.com <mailto:gabriela.gib...@gmail.com>> wrote:
> 
>     On Fri, Oct 3, 2014 at 11:50 AM, Pierre Smits
>     <pierre.sm...@gmail.com <mailto:pierre.sm...@gmail.com>>
>     wrote:
> 
>     > Hi,
>     >
>     > Recently we exchanged some thoughts (twitter and otherwise) regarding 
> the
>     > status of Apache top level projects and about how the reporting by the 
> ASF
>     > to the projects and the wider communities could be improved.
>     >
>     > Currently the status pages at http://status.apache.org regarding project
>     > health (commit activity and mailing lists) don't allow drill down into
>     > individual projects. Is it achievable to get this kind of functionality?
>     >
>     > Can we (as the ASF) also provide insights in number of people joining 
> and
>     > leaving the mailing lists of the projects and show what the trending 
> topics
>     > over the periods?
>     > But also reporting on average depth and width of mailing list threads?
>     >
>     > I do believe that these kind of insights will help monitoring project
>     > health and investigate where projects can improve regarding community
>     > building.
>     >
>     >
>     > I'm not so sure that mailing list subscription counts are very
>     representative -- I recently unsubscribed from almost every forum I had
>     ever joined because classification by labelling in gmail is a hit
>     and miss,
>     and the deluge of mails that were incorrectly sorted was too much.
> 
>     Instead, I use the web interfaces for those forums now.
> 
>     So, I would like to see the mailing list web interface be improved:
> 
>     Better thread navigation; and the ability to 'one-click
>     (un)subscribe' to a
>     given thread or a watch for keywords in the subject(subject to being
>     logged
>     in).  Being able to choose a digest or continuous format on a per-case
>     basis would also be nice.
> 
>     If that could be done, collected statistics about participation would be
>     far more reliable and informative.
> 
>     G
>     --
>     Visit my Coding Diary: http://gabriela-gibson.blogspot.com/
> 
> 

Reply via email to