Re: ASF booth at OpenSource Experience Paris

[Hervé Boutemy]

I'll be there for the 2 days, ready to help on the booth when useful

I've received my badge

@Olivier will you get your projector with the ASF projects logos app?
Do we need to prepare something else?

Regards,

Hervé

Le lundi 27 novembre 2023, 21:17:01 CET Olivier Heintz a écrit :
> Yes, there will be a booth, it's in two week, the 6-7th december
> 
> I can create some badge for all who wants to come,
> currently there are a badge for
> - you (ryan)
> - Hervé Boutemy
> - me
> 
> I will be present the two days but I will not be able to be on the booth all
> the time. It will be nice to get together for all the people who can come
> and spend some time with us.
> 
> Thanks
> 
> Le 13/11/2023 à 20:28, Ryan Skraba a écrit :
> > Hello!  If there's a booth at Open Source Experience, I can show up
> > and answer questions on one of the two days.  I have some Community
> > over Code Europe 2024 Bratislava stickers (June 3-5, CFP is open, be
> > there!)
> > 
> > Any news?  Anything else I can do to help out?  I see that we're
> > listed as exhibitors!
> > 
> > All my best, Ryan
> > 
> > On Wed, Oct 4, 2023 at 2:15 PM  wrote:
> >> On Wed, 2023-10-04 at 09:27 +0200, Olivier Heintz wrote:
> >>> This booth is free but it's a exchange contract between the booth and
> >>> the future ASF communication action for this event.
> >>> I have some question to the Event organization.
> >>> I can send the contract proposal to anyone want read it (it's in
> >>> french)
> >> 
> >> You're certainly welcome to send it, but cannot promise what will
> >> happen next, of course, until we read it.
> >> 
> >> Thanks.
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.or
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org





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

Re: The ASF at OpenSource Experience Paris, France

[Hervé Boutemy]

FYI, I will be able to join our booth only at 12h: I'll take all the swag that 
Sharan gave me during ApacheCON

see you tomorrow

Hervé

Le dimanche 16 octobre 2022, 16:21:05 CET Jean-Baptiste Onofré a écrit :
> Perfect !
> Thanks, I will try to print some.
> 
> Yes, Olivier should be there with the roller banner.
> 
> Regards
> JB
> 
> On Sun, Oct 16, 2022 at 4:17 PM Sharan Foga  wrote:
> > Hi JB
> > 
> > All the project logos are here https://apache.org/logos/  - these are the
> > ones I use for sticker printing. Herve has a few project ones but mainly
> > the general ASF ones for Community over code, Apache Way and the
> > foundation ones.
> > 
> > If Olivier is coming along then I think he has one of the ASF roller
> > banners.
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=81789772
> > 
> > Thanks
> > Sharan
> > 
> > On 2022/10/16 14:07:20 Jean-Baptiste Onofré wrote:
> > > Hey Sharan
> > > 
> > > Oh cool. Hervé will bring some then ;)
> > > 
> > > I can print some stickers myself (if you have the svg / high resolution
> > > files).
> > > 
> > > Thanks !
> > > Regards
> > > JB
> > > 
> > > Le dim. 16 oct. 2022 à 16:02, Sharan Foga  a écrit :
> > > > Hi JB
> > > > 
> > > > I'm not sure if I will make it over there this time but in New Orleans
> > > >  I
> > > > gave Herve some stickers and giveaways to bring over for the ASF booth
> > > > :-)
> > > > 
> > > > Thanks
> > > > Sharan
> > > > 
> > > > On 2022/10/11 12:31:53 Jean-Baptiste Onofré wrote:
> > > > > Hey Ryan,
> > > > > 
> > > > > More people, more fun ;)
> > > > > 
> > > > > So, you are more than welcome !
> > > > > 
> > > > > Thank you,
> > > > > Regards
> > > > > JB
> > > > > 
> > > > > On Mon, Oct 10, 2022 at 6:44 PM Ryan Skraba  wrote:
> > > > > > Hello!  Do you still need people?  I can be present at the table
> > > > > > for
> > > > > > one of the days!
> > > > > > 
> > > > > > Ryan
> > > > > > 
> > > > > > On Wed, Sep 28, 2022 at 10:32 AM Jean-Baptiste Onofré
> > > > > > 
> > > > 
> > > > wrote:
> > > > > > > Hi guys,
> > > > > > > 
> > > > > > > Thanks for your replies !
> > > > > > > 
> > > > > > > By the way, would it be possible to add OpenSource Experience on
> > > > > > > https://community.apache.org/calendars/ ?
> > > > > > > 
> > > > > > > Thanks !
> > > > > > > Regards
> > > > > > > JB
> > > > > > > 
> > > > > > > On Tue, Sep 27, 2022 at 2:58 PM Jean-Baptiste Onofré <
> > > > 
> > > > j...@nanthrax.net> wrote:
> > > > > > > > Hi guys,
> > > > > > > > 
> > > > > > > > The next OpenSource Experience event will stand November 8 & 9
> > > > 
> > > > this year:
> > > > > > > > https://www.opensource-experience.com/en/
> > > > > > > > 
> > > > > > > > It's a fairly large event about Open Source in Europe, located
> > > > > > > > in
> > > > 
> > > > Paris, France.
> > > > 
> > > > > > > > The exhibition has an area reserved for open source projects
> > > > > > > > and
> > > > 
> > > > foundations.
> > > > 
> > > > > > > > I took the lead to request a booth for The ASF. It has been
> > > > 
> > > > accepted.
> > > > 
> > > > > > > > It means we will have a booth dedicated to The ASF.
> > > > > > > > 
> > > > > > > > FIrst of all, if you are in Paris on November 8 or 9, and you
> > > > > > > > want
> > > > 
> > > > to
> > > > 
> > > > > > > > help at The ASF booth, please let me know (I will be at the
> > > > > > > > booth
> > > > 
> > > > most
> > > > 
> > > > > > > > of the time, but I will have to spend time at my company booth
> > > > 
> > > > too).
> > > > 
> > > > > > > > In order to "populate" the booth, do we have process to get
> > > > > > > > some
> > > > > > > > gadgets/swags (stickers, ...) ? Who can help on this front ?
> > > > > > > > 
> > > > > > > > Thanks in advance for your help !
> > > > > > > > 
> > > > > > > > Regards
> > > > > > > > JB
> > > > > > > 
> > > > > > > 
> > > > > > > -
> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > > 
> > > > > 
> > > > > -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > 
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org





---

Re: The ASF at OpenSource Experience Paris, France

[Hervé Boutemy]

thank you Jean Baptiste for the booth

I'll be there the 8th and morning of the 9th

Regards,

Hervé

Le mardi 27 septembre 2022, 14:58:06 CEST Jean-Baptiste Onofré a écrit :
> Hi guys,
> 
> The next OpenSource Experience event will stand November 8 & 9 this year:
> 
> https://www.opensource-experience.com/en/
> 
> It's a fairly large event about Open Source in Europe, located in Paris,
> France. The exhibition has an area reserved for open source projects and
> foundations.
> 
> I took the lead to request a booth for The ASF. It has been accepted.
> It means we will have a booth dedicated to The ASF.
> 
> FIrst of all, if you are in Paris on November 8 or 9, and you want to
> help at The ASF booth, please let me know (I will be at the booth most
> of the time, but I will have to spend time at my company booth too).
> 
> In order to "populate" the booth, do we have process to get some
> gadgets/swags (stickers, ...) ? Who can help on this front ?
> 
> Thanks in advance for your help !
> 
> Regards
> JB
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org





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

Re: The projects.apache.org site confuses basic principles

[Hervé BOUTEMY]

> > I seem to remember struggling with this specific naming decision when the
> > projects.a.o site was first put up.
> This was setup in the PRC, correct? (IIRC - PRC was split into comdev,
> conference, trademark, and press about 12 years ago)

I did that naming research and implementation in projects.a.o 5 years ago, and 
shared with Comdev member the issues during ApacheCon Sevilla

Yes, we have naming issues particularly on
  Committee ~ PMC ~ TLP ~ sometimes "project" [1]
vs
  project ~ sub-project

see the "Projects by Committee" page to see which TLPs declare many sub-
projects [2]

I won't dig into the "product" semantics (some TLPs have much more Git 
repositories than they have declared sub-projects: what is effective product 
granularity?).
Nor dig into the question of how TLPs declare (or not) their TLP data (with 
RDF files) and their sub-projects (with DOAP files).

To me, TLP and sub-projects are the words that clarify things internally when 
we speak at Apache level, but these words were not well accepted during 
discussons.

I did a main naming choice on projects.a.o: Committee vs Project
And I tried to use it consistently in the site, while making explicit in the 
main page "Committees evolution (also called PMCs or Top Level Projects)"


If someone wants to take a new pass at it, I'm open: but experience shows that 
it's hard to have a simple wording that works in any case with every project 
(TLPs with single project and single Git repo, vs TLPs with a few sub-projects 
and many Git repositories, and I don't name Subversion because it's harder to 
count Subversion "roots"...)

At least, I'm happy that after 5 years, projects.a.o is now a reference list 
that people are interested to improve :)

Regards,

Hervé


[1] https://www.apache.org/index.html#projects-list

[2] https://projects.apache.org/projects.html?committee



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

Re: Open Source Experience Paris 2021, 9-10th Nov.

[Hervé BOUTEMY]

Hi Olivier,

Yes, I'll be there, you can count on me: being alone at a booth is really not 
funny!

Let's contact other french people we know, to have a chance to meet more 
people given the new life that is starting :)

See you soon

Hervé

Le samedi 16 octobre 2021, 17:10:01 CEST Olivier Heintz a écrit :
> Hello everyone,
> 
> There will be a ASF booth for the 2 days, I will be there the 2 days, but I
> hope there will be other peoples for helping me ;-) @Herve do you know if
> you could be available for this date or part or them.
> 
> The first days 9th, there is the BlueHats community(French government
> employees working on or contributing to an OpenSource project) days and if
> there is an other people available for the booth I could participate to it
> and explain the ApacheWays.
> 
> Even if someone is only available for a few hours, I'll take it.
> 
> I've been looking for a "list" of French ASF contributors - committer -
> members -  but I can't find where it is possible to see the "location"
> of ASF committers.
> Does anyone know how to do this?
> If yes, I will send them a copy of this mail.
> 
> Olivier
> 
> Le 08/09/2021 à 21:52, Olivier Heintz a écrit :
> > Hello everyone,
> > 
> > This year, there is a new format for the French Open Source Event
> > https://www.opensource-experience.com/en/
> > 
> > It's the 9 & 10 November 2021
> > 
> > There will be a dedicate part for non profit organization, and it's
> > possible to have a booth for this event for the Apache foundation.
> > 
> > Is there someone available on those dates to be with me for present and
> > explain the Apache foundation and the Apache Way.
> > 
> > Olivier
> > 
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org





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

Re: Data inconsistency in projects.apache.org

[Hervé BOUTEMY]

yes, I'm convinced some data can be extracted automatically

but I also know that some data can't
for example:
- for committees with multiple projects, like 
https://projects.apache.org/projects.html?committee#commons
- for projects still using svn
- the definition of languages and categories and the association of projects to 
these:
  https://projects.apache.org/projects.html?category
  https://projects.apache.org/projects.html?language

in the past (the previous projects.apache.org), some tooling was provided to 
PMCs to easily generate a first project description without reading too much.

I now see Sebb (I suppose) did some hard work to integrate this tool:
https://projects.apache.org/create.html

It could probably be improved to provide pre-filled form or some form of 
autocomplete
and of course, letting committees know thereis some tooling to help them 
maintain their data could help

Regards,

Hervé

Le samedi 28 mars 2020, 01:20:05 CET Dave Fisher a écrit :
> See http://incubator.apache.org/clutch/tuweni
> 
> The repositories are actual and are updated from
> gitbox.apache.org/repositories.json
> 
> The releases are from dist.apache.org/repos/dist/release and are exactly
> what is available.
> 
> Other items on the page are either from a podling status file or other bits
> of information including the podlings.xml.
> 
> This information can be a service to the projects and the foundation.
> 
> Sent from my iPhone
> 
> > On Mar 27, 2020, at 2:04 PM, Hervé BOUTEMY  wrote:
> > 
> > there are many more parts, see some examples of human-readable output:
> > https://projects.apache.org/project.html?accumulo
> > https://projects.apache.org/project.html?calcite
> > 
> > Le vendredi 27 mars 2020, 21:44:56 CET Dave Fisher a écrit :
> >> metadata for project releases is discoverable from the dist in svn. It is
> >> already done for podlings in the Incubator in the clutch analysis.
> >> 
> >> It is python. I can provide some help late next week.
> >> 
> >> Sent from my iPhone
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org





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

Re: Data inconsistency in projects.apache.org

[Hervé BOUTEMY]

there are many more parts, see some examples of human-readable output:
https://projects.apache.org/project.html?accumulo
https://projects.apache.org/project.html?calcite

Le vendredi 27 mars 2020, 21:44:56 CET Dave Fisher a écrit :
> metadata for project releases is discoverable from the dist in svn. It is
> already done for podlings in the Incubator in the clutch analysis.
> 
> It is python. I can provide some help late next week.
> 
> Sent from my iPhone




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

Re: Data inconsistency in projects.apache.org

[Hervé BOUTEMY]

Le vendredi 27 mars 2020, 21:19:56 CET sebb a écrit :
> > > That way, over time, we'd eventually have all of those files in one
> > > place, making them easier to find and update.
> > 
> > find = 2 files (1 for committees, 1 for projects)
> 
> May be more than one for projects.
> e.g. Commons.

I was not clear, here are the 2 files:
https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/committees.xml
https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/projects.xml

> > On letting PMC RDF files go outside the centralised approach, I'd be
> > curious to check if the 4 PMCs that chose to host outside of projects.a.o
> > did that to fill more data, or if they just felt that they'd host this
> > file the same way they did with project DOAP file.
> I suggest dropping them entirely.
yes, I suppose the PMC RDF content could be fully extracted from other sources: 
the only hard part is the charter, that you seem to have already extracted 
automatically

dropping PMC RDF files would simplify the discussion, since only project DOAP 
files would remain

big +1: a good step in the right direction of simplification to enable us to 
focus on the hard part = project DOAP files

Regards,

Hervé



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

Re: Data inconsistency in projects.apache.org

[Hervé BOUTEMY]

Le vendredi 27 mars 2020, 20:11:33 CET Rich Bowen a écrit :
> For context, I'm trying to address Sally's complaint that the data on
> projects.a.o is inconsistent, out of date, and wonky.
yes, I like this objective

> I am very willing
> to reach out to various projects about data updates (and am doing that
> already for other things - namely, the stuff on
> https://whimsy.apache.org/site/) but the "where is our data" question
> not having one consistent answer is a little frustrating.
this is where the mix between committee oriented data vs "technical" project 
data starts to hurt: projects DOAP files are technical details, that are to be 
delegated

you can see the difference by looking at Committees page https://
projects.apache.org/committees.html vs Projects page https://
projects.apache.org/projects.html that can be sorted by Category and 
Programming Language

> 
> I think, though, I now know where to go to look it up.





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

Re: Data inconsistency in projects.apache.org

[Hervé BOUTEMY]

Le vendredi 27 mars 2020 20:29:14 CET, vous avez écrit :
> On 3/27/20 3:07 PM, Hervé BOUTEMY wrote:
> > It's good to see some interest back on DOAP files content ad organisation,
> > now that the projects.apache.org rendering makes them really useful: a
> > few years ago, trying to open any discussion on that was deemed to
> > failure. But any change is hard, since every PMC will have to be
> > involved.
> 
> What if we - and I'm perfectly prepared to be told "You can't do that
> because ..." - fetched remote (ie, project-hosted) doap files, a few at
> a time, and move them to the central repo, and as we do that, we go talk
> to projects individually, telling them that we're doing it, and why, and
> what the new process is for updating. Yes, I'm volunteering to do that
> outreach.
you can, but I don't see the benefit of this hard work

> 
> That way, over time, we'd eventually have all of those files in one
> place, making them easier to find and update.
find = 2 files (1 for committees, 1 for projects)

> 
> I'm leaving the file format question for someone else entirely. I am far
> less concerned about that, than about ensuring that the files are easily
> found and updated.
my point about "PMC RDF files" vs "projects DOAP files" is not a question of 
format, but a question of amount of data and who would have real knowledge to 
update content:
- PMC RDF files are very light, rarely updated, and contain data that are 
really foundation-centric
- projects DOAP files contain a lot more data, can/should be often updated, 
with data that are really to be delegated to PMCs given they are more technical 
details on code

That's why I really think keeping centralised PMC RDF files and decentralised 
projects DOAP files is a good idea.

IMHO, centralising project DOAP files would be a hard task with low benefit, 
and even counter productive effect on having every PMC responsible for the 
content, that is technical.

On letting PMC RDF files go outside the centralised approach, I'd be curious to 
check if the 4 PMCs that chose to host outside of projects.a.o did that to fill 
more data, or if they just felt that they'd host this file the same way they 
did with project DOAP file.

Regards,

Hervé

> 
> --Rich





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

Re: Data inconsistency in projects.apache.org

[Hervé BOUTEMY]

Le vendredi 27 mars 2020, 19:04:28 CET Rich Bowen a écrit :
> > If any changes are made, I strongly recommend centralising the data files.
> > DOAP files maintained in project data areas often get moved, and the
> > project forgets to update the entry in projects.xml
> > Also, sometimes edits to DOAP files have syntax errors.
> > My experience is that it can be very hard work getting projects to fix
> > errors, whereas if DOAPs were centrally located, anyone could fix
> > errors.
> 
> So, while to me that seems like an obvious and enormous improvement, my
> understanding is that this was proposed before and someone (I understood
> it was you?) vetoed the change. So I'm a teensy bit confused.

on PMC RDF files, it was fully centralised, and I see now that some PMCs chose 
to host externally
on projects DOAP files, it is de-centralised for a long time
(notice: "PMC RDF files" vs "projects DOAP files")

I don't remember precisely last discussions, but I am one who wants to keep 
DOAP files de-centralised: my rationale is that projects DOAP files contain a 
lot of data that can be updated often (like releases)

PMC RDF files require a lot less maintenance: keeping them centralised seemed 
sufficient for a long time

It's good to see some interest back on DOAP files content ad organisation, now 
that the projects.apache.org rendering makes them really useful: a few years 
ago, trying to open any discussion on that was deemed to failure. But any 
change is hard, since every PMC will have to be involved.

Regards,

Hervé



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

Re: Data inconsistency in projects.apache.org

[Hervé BOUTEMY]

please start by reading the human-oriented explanation:
https://projects.apache.org/about.html

this should ease the deep dive into data behind the recurring "Committees vs 
Projects" discussion

Regards,

Hervé

Le vendredi 27 mars 2020, 14:43:52 CET Rich Bowen a écrit :
> I'm trying to understand the twisty maze of data sources that fuel
> projects.apache.org and either I'm confused, or there's some
> inconsistency in how this all fits together.
> 
> I'll start with just one data source for now, so that I don't muddle
> multiple things together.
> 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/data/commi
> ttees.xml
> 
> 
> This file has a list of rdf files which are supposed to be in the
> committees/ subdirectory. The file itself says:
> 
> This list should agree with the files in the directory committees/
> 
> However, in addition to the entries that look like:
> 
>committees/any23.rdf
> 
> there are also lines that look like:
> 
>http://flex.apache.org/pmc_Flex.rdf
> 
> (4 of them, for whatever that's worth - flex, ofbiz, plc4x, and tez)
> 
> Is that correct? Or is that not how the data is supposed to be stored?
> 
> Meanwhile, committees.xml contains 209 projects:
> 
> grep location committees.xml| grep -vc Retired
> 209
> 
> while the committees/ directory contains just 206 rdf files:
> 
> ls committees/*.rdf| wc -l
> 206
> (Note, one of those files is _template.rdf, so it's really 205, and 205
> + 4 = 209, so at least everything else matches up.)





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

[RB] Working on Reproducible Builds for ASF projects

[Hervé BOUTEMY]

Hi,

As discussed in "Binary channels" thread on legal-discuss [1], Reproducible 
Builds [2] is something that should be very interesting to improve management 
of convenience binaries at ASF.

Reproducible Builds started with but is not limited to Linux distributions: in 
ASF, interesting case would be language-specific distributions like Maven 
Central, PyPI, npmjs, or even Dockerhub.

Some work has started at Reproducible Builds on the JVM [3]. That should 
happen also for other "languages".

Are there Apache projects interested in working together to share experience 
and improvements?

Regards,

Hervé

[1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/

[2] https://reproducible-builds.org/

[3] https://reproducible-builds.org/docs/jvm/



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

Re: Update on logo hunt

[Hervé BOUTEMY]

Hi,

great work!

why not integrate content in existing projects directory?
https://projects.apache.org/

And I don't know how the original logo url could be added to DOAP files...

Regards,

Hervé

Le vendredi 24 août 2018, 14:39:11 CEST Daniel Gruno a écrit :
> Hi all,
> 
> Logos are slowly ticking in and being processed.
> I have a mockup of a 'logo central' site working, which you can see at
> https://logos.humbedooh.com/ - it has all the images that are available
> on scalable formats (svg, eps, ai etc) with various versions available.
> Images are automatically processed from SVN every hour on the hour, so
> any new additions should show up within an hour.
> 
> I'll work on adding a "how do I submit my logo" part of this as time
> permits. Hopefully this will spur some more logos being added :) And if
> enough traction, we can put this and the automated process on a comdev VM.
> 
> With regards,
> Daniel.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org





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

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

uh, the move to trunk discarded the whole history before!

That's not what I expected for a a svn2git mirror

I'm not proficient enough in Git and svn2git, I hope infra can help, but it 
would be good if we could have the new trunk history appended after the whole 
pre-trunk history...

Regards,

Hervé

Le dimanche 29 avril 2018, 09:40:08 CEST sebb a écrit :
> Top-posting
> 
> I have moved SVN down a level to trunk/ and updated the workspace on
> projects.a.o to use it.
> Its pubsub seems to be working.
> 
> The next set of cronjobs run from midnight to 4am (UTC) so we shall
> see tomorrow if anything needs to be tweaked.
> 
> S.
> 
> On 29 April 2018 at 07:04, sebb  wrote:
> > On 26 April 2018 at 01:02, sebb  wrote:
> >> Looks like there is a bit more to it.
> >> 
> >> asf-auth template needs to be updated to give projects_role access to
> >> the new directory.
> >> This can be done by adding the new directory name and later dropping
> >> the old one.
> > 
> > The asf-auth update has been applied, so the code will be able to
> > update SVN in the new location.
> > 
> >> I don't yet know how to update projects-vm safely.
> >> 
> >> On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
> >>> no objection for me: what is important is to keep the machine running
> >>> the web server synchronized with the change
> >>> 
> >>> Regards,
> >>> 
> >>> Hervé
> >>> 
> >>> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
> >>>> It looks like we need to move the contents of
> >>>> 
> >>>> https://svn.apache.org/repos/asf/comdev/projects.apache.org
> >>>> 
> >>>> to
> >>>> 
> >>>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
> >>>> 
> >>>> [No need to do the same for reporter, as it already uses a trunk
> >>>> directory]
> >>>> 
> >>>> AFAICT this should not affect the projects.a.o site.
> >>>> The pubsub script that pulls in updates only looks for the
> >>>> comdev/projects.apache.org prefix.
> >>>> (As it does for reporter)
> >>>> 
> >>>> Moving projects to the trunk directory would give it the same layout
> >>>> as reporter.
> >>>> It would also allow the use of tags/ and branches/ sibling directories.
> >>>> 
> >>>> Are there objections to moving projects.a.o down a level?
> >>>> 
> >>>> On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
> >>>> > Jira issue created:
> >>>> > https://issues.apache.org/jira/browse/INFRA-16355
> >>>> > 
> >>>> > Regards,
> >>>> > 
> >>>> > Hervé
> >>>> > 
> >>>> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
> >>>> >> ok, I don't see any remaining objection
> >>>> >> 
> >>>> >> I'll ask for svn2git read-only Git+GitHub mirrors.
> >>>> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the
> >>>> >> git
> >>>> >> repo "comdev-community.apache.org" to match other
> >>>> >> "comdev-*.apache.org"
> >>>> >> 
> >>>> >> This will ease people understanding that comdev's site is
> >>>> >> community.apache.org (and not comdev.apache.org...)
> >>>> >> 
> >>>> >> Regards,
> >>>> >> 
> >>>> >> Hervé
> >>>> >> 
> >>>> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
> >>>> >> > What about creating a Git/GitHub svn2git mirror for
> >>>> >> > projects.apache.org?
> >>>> >> > This would be our first Git repo for community/comdev: I don't
> >>>> >> > know
> >>>> >> > which
> >>>> >> > prefix we should use...
> >>>> >> > 
> >>>> >> > Any objection?
> >>>> >> > 
> >>>> >> > Perhaps we can do the same for the 3 other locations in svn
> >>>> >> > https://projects.apache.org/project.html?comdev-community_developm
> >>>> >> > ent
> >>>

Re: New ASF Member: Piergiorgio Lucidi

[Hervé BOUTEMY]

congrats Piergiorgio!

when can we meet at a conference?
need to have a drink!
:)

Regards,

Hervé

Le jeudi 3 mai 2018, 22:44:09 CEST Piergiorgio Lucidi a écrit :
> Thank you all for your messages!
> 
> I'm very proud and honored to be part of the ASF, this is absolutely
> awesome :)
> A special thank to Sharan for proposing my nomination during the meeting
> and to Bertrand for his vote.
> 
> Cheers,
> PJ
> 
> 2018-05-02 22:16 GMT+02:00 Sharan Foga :
> > Hi All
> > 
> > In today’s announcement of all our new ASF members – one name that I’m
> > sure you will recognise from our ComDev PMC is in there too ---
> > Piergiorgio
> > Lucidi!
> > 
> > https://s.apache.org/D6iz
> > 
> > Please join me in congratulating PJ on becoming an ASF member!
> > 
> > Thanks
> > Sharan
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org



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

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

no objection for me: what is important is to keep the machine running the web 
server synchronized with the change

Regards,

Hervé

Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
> It looks like we need to move the contents of
> 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org
> 
> to
> 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
> 
> [No need to do the same for reporter, as it already uses a trunk directory]
> 
> AFAICT this should not affect the projects.a.o site.
> The pubsub script that pulls in updates only looks for the
> comdev/projects.apache.org prefix.
> (As it does for reporter)
> 
> Moving projects to the trunk directory would give it the same layout
> as reporter.
> It would also allow the use of tags/ and branches/ sibling directories.
> 
> Are there objections to moving projects.a.o down a level?
> 
> On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
> > Jira issue created:
> > https://issues.apache.org/jira/browse/INFRA-16355
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
> >> ok, I don't see any remaining objection
> >> 
> >> I'll ask for svn2git read-only Git+GitHub mirrors.
> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git
> >> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
> >> 
> >> This will ease people understanding that comdev's site is
> >> community.apache.org (and not comdev.apache.org...)
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
> >> > What about creating a Git/GitHub svn2git mirror for
> >> > projects.apache.org?
> >> > This would be our first Git repo for community/comdev: I don't know
> >> > which
> >> > prefix we should use...
> >> > 
> >> > Any objection?
> >> > 
> >> > Perhaps we can do the same for the 3 other locations in svn
> >> > https://projects.apache.org/project.html?comdev-community_development
> >> > 
> >> > Regards,
> >> > 
> >> > Hervé
> >> > 
> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> > > Vincent Tuybens created COMDEV-288:
> >> > > --
> >> > > 
> >> > >  Summary: Request "Projects Directory" migration to GIT
> >> > >  
> >> > >  Key: COMDEV-288
> >> > >  URL:
> >> > >  https://issues.apache.org/jira/browse/COMDEV-288
> >> > >  
> >> > >  Project: Community Development
> >> > >   
> >> > >   Issue Type: SVN->GIT Migration
> >> > >   Components: Projects Tool
> >> > >   
> >> > > Reporter: Vincent Tuybens
> >> > > 
> >> > > Dear all,
> >> > > 
> >> > > is it possible for you to plan SVN to GIT migration for "Projects
> >> > > Directory" project ?
> >> > > 
> >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac
> >> > > he.
> >> > > or
> >> > > g/ {color}]
> >> > > 
> >> > > Thank you,
> >> > > 
> >> > > Regards.
> >> > > 
> >> > > 
> >> > > 
> >> > > --
> >> > > This message was sent by Atlassian JIRA
> >> > > (v7.6.3#76005)
> >> > > 
> >> > > -
> >> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > > For additional commands, e-mail: dev-h...@community.apache.org
> >> > 
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > For additional commands, e-mail: dev-h...@community.apache.org
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: Is DOAP still a thing?

[Hervé BOUTEMY]

Le jeudi 19 avril 2018, 00:05:01 CEST Christopher a écrit :
[...]
> > > Yeah. That's great, but as I pointed out, it's useless to do so if they
> > > aren't utilized for any other purpose.
> > 
> > As I keep saying, the DOAPs *ARE* used to build the p.a.o pages.
> 
> Okay, okay. Sorry, Sebb. You're right. It does seem to still be in use for
> building some portions of p.a.o. I just didn't see any evidence of that,
> and could not find any documentation on *how* it is used to build them.
perhaps I should just add that PMC RDF data files are used to build Committees 
pages: https://projects.apache.org/committees.html (Committee is a synonym 
here for PMC)
and projects DOAP files are used to build Projects pages:
https://projects.apache.org/projects.html

it's not so obvious since the difference between Committe and Project is not 
so obvious

I'm happy to have some feedback on the documentation written, that I'm not 
sure many people read: I'll be happy to improve it given on the feedback

> 
> You are right. I was mistaken. I had not spent enough time on the site to
> understand how it is used, and it was not obvious to me that any
> functionality was missing when the DOAP file was missing. Sorry for the
> misunderstanding on my part.
> 
> After some more time spent on the site, I was able to see some portions
> which don't work if the DOAP is missing. Specifically, I can now see that
> it is used for grouping projects by language, by category, and listing
> releases (which is the information I was asking for, and which would be
> useful to add to [2], along with any other way it is used that I did not
> observe.)
> 
> I do think it is preferred that p.a.o get release information from
> reporter.a.o instead... it would make maintaining DOAP simpler, and reduce
> the burden on developers to maintain a duplicate dataset.
I confess that Branko's remark about "Semantic Web aficionados appear to have 
vanished into the space between microservices" seems relevant...
the idea behind using some universal format, and not just Apache internal 
tooling, was appealing: everything that is done magically by internal tooling 
has drawbacks.
But for sure, the release part is the most hard to manually maintain part.

> Thank you for your persistence in educating me. I did eventually get there.
> Sorry if my confusion and ignorance caused any unnecessary strife. :)
It's good to have feedback and interest, even if the interest contains 
criticism: it's constructive feedback

Regards,

Hervé

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

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

Jira issue created:
https://issues.apache.org/jira/browse/INFRA-16355

Regards,

Hervé

Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
> ok, I don't see any remaining objection
> 
> I'll ask for svn2git read-only Git+GitHub mirrors.
> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git
> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
> 
> This will ease people understanding that comdev's site is
> community.apache.org (and not comdev.apache.org...)
> 
> Regards,
> 
> Hervé
> 
> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
> > What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> > This would be our first Git repo for community/comdev: I don't know which
> > prefix we should use...
> > 
> > Any objection?
> > 
> > Perhaps we can do the same for the 3 other locations in svn
> > https://projects.apache.org/project.html?comdev-community_development
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > > Vincent Tuybens created COMDEV-288:
> > > --
> > > 
> > >  Summary: Request "Projects Directory" migration to GIT
> > >  
> > >  Key: COMDEV-288
> > >  URL: https://issues.apache.org/jira/browse/COMDEV-288
> > >  
> > >  Project: Community Development
> > >   
> > >   Issue Type: SVN->GIT Migration
> > >   Components: Projects Tool
> > >   
> > > Reporter: Vincent Tuybens
> > > 
> > > Dear all,
> > > 
> > > is it possible for you to plan SVN to GIT migration for "Projects
> > > Directory" project ?
> > > 
> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.
> > > or
> > > g/ {color}]
> > > 
> > > Thank you,
> > > 
> > > Regards.
> > > 
> > > 
> > > 
> > > --
> > > This message was sent by Atlassian JIRA
> > > (v7.6.3#76005)
> > > 
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

ok, I don't see any remaining objection

I'll ask for svn2git read-only Git+GitHub mirrors.
Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git repo 
"comdev-community.apache.org" to match other "comdev-*.apache.org"

This will ease people understanding that comdev's site is community.apache.org 
(and not comdev.apache.org...)

Regards,

Hervé

Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
> What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> This would be our first Git repo for community/comdev: I don't know which
> prefix we should use...
> 
> Any objection?
> 
> Perhaps we can do the same for the 3 other locations in svn
> https://projects.apache.org/project.html?comdev-community_development
> 
> Regards,
> 
> Hervé
> 
> Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > Vincent Tuybens created COMDEV-288:
> > --
> > 
> >  Summary: Request "Projects Directory" migration to GIT
> >  
> >  Key: COMDEV-288
> >  URL: https://issues.apache.org/jira/browse/COMDEV-288
> >  
> >  Project: Community Development
> >   
> >   Issue Type: SVN->GIT Migration
> >   Components: Projects Tool
> >   
> > Reporter: Vincent Tuybens
> > 
> > Dear all,
> > 
> > is it possible for you to plan SVN to GIT migration for "Projects
> > Directory" project ?
> > 
> > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.or
> > g/ {color}]
> > 
> > Thank you,
> > 
> > Regards.
> > 
> > 
> > 
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

yes, they are not mergeable at Git level (since it will be read-only)
but they are mergeable at svn level, the same way that we merge patches 
attached to Jira issues (when people take time to create such patches and 
attach, which nowadays does not happen much): every GitHub PR can be seen as a 
patch or diff (I don't remember if one is best suited than the other)

example:
PR: https://github.com/apache/maven-wagon/pull/47
patch: https://github.com/apache/maven-wagon/pull/47.patch
diff: https://github.com/apache/maven-wagon/pull/47.diff

not as convenient for the Comdev team as if we fully switch to Git, but like 
explained to Sebb, svn2git mirror is a necessary first step that lowers impact 
before thinking about doing next steps or not.
For the team, it really behaves as if we totally stay with svn: this Git 
mirror is just a new source of patches that are easier for contributors to 
create and submit (through Pull Requests)

But for sure, fully switching to Git to get Git-mergeable Pull Requests for 
the team can be useful in the future: we'll see that later, seeing also other 
side impacts (on hosts for example)

Regards,

Hervé

Le jeudi 5 avril 2018, 03:00:40 CEST Maxim Solodovnik a écrit :
> The PRs created for read-only hit are not "mergeable"
> 
> WBR, Maxim
> (from mobile, sorry for the typos)
> 
> On Thu, Apr 5, 2018, 05:34 Hervé BOUTEMY  wrote:
> > there is a little misunderstanding: I'm not talking about fully switching
> > from
> > svn to git
> > I'm talking about keeping svn as canonical repository but adding a
> > read-only
> > git mirror like done on many svn repositories [1]
> > 
> > This does not change anything to the host configuration, but adds a GitHub
> > mirror for external people to contribute through GitHub Pull Requests,
> > which
> > are so much easier to submit than svn patch attached to a Jira issue: this
> > will give a chance to get more contributions.
> > 
> > Later on, we can decide to switch to Git (with gitwcsub acting like
> > currently
> > svnwcsub), but that will be another choice to do in another time.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1] http://git.apache.org/
> > 
> > Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> > > On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> > > > What about creating a Git/GitHub svn2git mirror for
> > 
> > projects.apache.org?
> > 
> > > > This would be our first Git repo for community/comdev: I don't know
> > 
> > which
> > 
> > > > prefix we should use...
> > > > 
> > > > Any objection?
> > > 
> > > What are the benefits to using Git over SVN?
> > > Do they outweigh the costs?
> > > Who gets the benefit, and who pays the costs?
> > > 
> > > ==
> > > 
> > > Note that projects.a.o actually updates its own code repo using a role
> > > account. I don't know if that can be done in Git.
> > > It took quite a bit of work to ensure that the updates did not result
> > > in a locked workspace.
> > > (This used to happen regularly at the beginning)
> > > 
> > > Also, the projects.a.o and reporter.a.o hosts share the same VM.
> > > They would need to move together.
> > > 
> > > And of course the VM puppet definition will need to be updated.
> > > It's more complicated than a simple pubsub operation.
> > > 
> > > > Perhaps we can do the same for the 3 other locations in svn
> > > > https://projects.apache.org/project.html?comdev-community_development
> > > > 
> > > > Regards,
> > > > 
> > > > Hervé
> > > > 
> > > > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > > >> Vincent Tuybens created COMDEV-288:
> > > >> --
> > > >> 
> > > >>  Summary: Request "Projects Directory" migration to GIT
> > > >>  
> > > >>  Key: COMDEV-288
> > 
> > > >>  URL:
> > https://issues.apache.org/jira/browse/COMDEV-288
> > 
> > > >>  Project: Community Development
> > > >>   
> > > >>   Issue Type: SVN->GIT Migration
> > > >>   Components: Projects Tool
> > > >>   
> > > >> Reporter: Vincent Tuybens
> > > >> 
> > > >> Dear all,
> > > &

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

Le jeudi 5 avril 2018, 00:42:57 CEST sebb a écrit :
> On 4 April 2018 at 23:34, Hervé BOUTEMY  wrote:
> > there is a little misunderstanding: I'm not talking about fully switching
> > from svn to git
> > I'm talking about keeping svn as canonical repository but adding a
> > read-only git mirror like done on many svn repositories [1]
> 
> The JIRA said otherwise...
yes, external people nowadays just think "switch to Git" et voilà.
But I have a long experience on Maven (more than 5 years to to the near full 
migration [2]), and I know that it does not happen like this: there are steps 
to have the team find advantages along the journey, letting time to learn and 
do progressive adoption
This is how I naturally transformed the initial typical request: into the 
typical first step

[2] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration

> 
> > This does not change anything to the host configuration, but adds a GitHub
> > mirror for external people to contribute through GitHub Pull Requests,
> > which are so much easier to submit than svn patch attached to a Jira
> > issue: this will give a chance to get more contributions.
> 
> OK, fine.
> 
> > Later on, we can decide to switch to Git (with gitwcsub acting like
> > currently svnwcsub), but that will be another choice to do in another
> > time.
> 
> That will be a lot of work.
We'll see it later: for sure, it's more impact, then requires to be prepared.
svn 2 git mirror is a good first step, that is required if we do the next steps 
or not

> 
> > Regards,
> > 
> > Hervé
> > 
> > [1] http://git.apache.org/
> > 
> > Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> >> On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> >> > What about creating a Git/GitHub svn2git mirror for
> >> > projects.apache.org?
> >> > This would be our first Git repo for community/comdev: I don't know
> >> > which
> >> > prefix we should use...
> >> > 
> >> > Any objection?
> >> 
> >> What are the benefits to using Git over SVN?
> >> Do they outweigh the costs?
> >> Who gets the benefit, and who pays the costs?
> >> 
> >> ==
> >> 
> >> Note that projects.a.o actually updates its own code repo using a role
> >> account. I don't know if that can be done in Git.
> >> It took quite a bit of work to ensure that the updates did not result
> >> in a locked workspace.
> >> (This used to happen regularly at the beginning)
> >> 
> >> Also, the projects.a.o and reporter.a.o hosts share the same VM.
> >> They would need to move together.
> >> 
> >> And of course the VM puppet definition will need to be updated.
> >> It's more complicated than a simple pubsub operation.
> >> 
> >> > Perhaps we can do the same for the 3 other locations in svn
> >> > https://projects.apache.org/project.html?comdev-community_development
> >> > 
> >> > Regards,
> >> > 
> >> > Hervé
> >> > 
> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> >> Vincent Tuybens created COMDEV-288:
> >> >> --
> >> >> 
> >> >>  Summary: Request "Projects Directory" migration to GIT
> >> >>  
> >> >>  Key: COMDEV-288
> >> >>  URL: https://issues.apache.org/jira/browse/COMDEV-288
> >> >>  
> >> >>  Project: Community Development
> >> >>   
> >> >>   Issue Type: SVN->GIT Migration
> >> >>   Components: Projects Tool
> >> >>   
> >> >> Reporter: Vincent Tuybens
> >> >> 
> >> >> Dear all,
> >> >> 
> >> >> is it possible for you to plan SVN to GIT migration for "Projects
> >> >> Directory" project ?
> >> >> 
> >> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apach
> >> >> e.o
> >> >> rg/ {color}]
> >> >> 
> >> >> Thank you,
> >> >> 
> >> >> Regards.
> >> >> 
> >> >> 
> >> >> 
> >> >> --
> >> >> This message was sent by Atlassian JIRA
> >> >> (v7.6.3#76005)
> >> >

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

there is a little misunderstanding: I'm not talking about fully switching from 
svn to git
I'm talking about keeping svn as canonical repository but adding a read-only 
git mirror like done on many svn repositories [1]

This does not change anything to the host configuration, but adds a GitHub 
mirror for external people to contribute through GitHub Pull Requests, which 
are so much easier to submit than svn patch attached to a Jira issue: this 
will give a chance to get more contributions.

Later on, we can decide to switch to Git (with gitwcsub acting like currently 
svnwcsub), but that will be another choice to do in another time.

Regards,

Hervé

[1] http://git.apache.org/

Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> > What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> > This would be our first Git repo for community/comdev: I don't know which
> > prefix we should use...
> > 
> > Any objection?
> 
> What are the benefits to using Git over SVN?
> Do they outweigh the costs?
> Who gets the benefit, and who pays the costs?
> 
> ==
> 
> Note that projects.a.o actually updates its own code repo using a role
> account. I don't know if that can be done in Git.
> It took quite a bit of work to ensure that the updates did not result
> in a locked workspace.
> (This used to happen regularly at the beginning)
> 
> Also, the projects.a.o and reporter.a.o hosts share the same VM.
> They would need to move together.
> 
> And of course the VM puppet definition will need to be updated.
> It's more complicated than a simple pubsub operation.
> 
> > Perhaps we can do the same for the 3 other locations in svn
> > https://projects.apache.org/project.html?comdev-community_development
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> Vincent Tuybens created COMDEV-288:
> >> --
> >> 
> >>  Summary: Request "Projects Directory" migration to GIT
> >>  
> >>  Key: COMDEV-288
> >>  URL: https://issues.apache.org/jira/browse/COMDEV-288
> >>  
> >>  Project: Community Development
> >>   
> >>   Issue Type: SVN->GIT Migration
> >>   Components: Projects Tool
> >>   
> >> Reporter: Vincent Tuybens
> >> 
> >> Dear all,
> >> 
> >> is it possible for you to plan SVN to GIT migration for "Projects
> >> Directory" project ?
> >> 
> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.o
> >> rg/ {color}]
> >> 
> >> Thank you,
> >> 
> >> Regards.
> >> 
> >> 
> >> 
> >> --
> >> This message was sent by Atlassian JIRA
> >> (v7.6.3#76005)
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

What about creating a Git/GitHub svn2git mirror for projects.apache.org?
This would be our first Git repo for community/comdev: I don't know which 
prefix 
we should use...

Any objection?

Perhaps we can do the same for the 3 other locations in svn
https://projects.apache.org/project.html?comdev-community_development

Regards,

Hervé

Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> Vincent Tuybens created COMDEV-288:
> --
> 
>  Summary: Request "Projects Directory" migration to GIT
>  Key: COMDEV-288
>  URL: https://issues.apache.org/jira/browse/COMDEV-288
>  Project: Community Development
>   Issue Type: SVN->GIT Migration
>   Components: Projects Tool
> Reporter: Vincent Tuybens
> 
> 
> Dear all,
> 
> is it possible for you to plan SVN to GIT migration for "Projects Directory"
> project ?
> 
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/
> {color}]
> 
> Thank you,
> 
> Regards.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: How does Apache POI work?

[Hervé BOUTEMY]

Hi Sal,

Apache POI website http://poi.apache.org/ is what you're looking for.

Regards,

Hervé

Le samedi 2 décembre 2017, 14:01:09 CET Anastacio Meza a écrit :
> Hello,
> 
> My name is Anastacio Meza, but I go by Sal for short.  I have been trying
> to find information on how A.POI interfaces with excel.  I am a computer
> science major and am interested in how this works.  From what I've learned,
> and I can't confirm it, A.POI is a collection of Java, and VBA commands.
> A.POI communicates with windows OS via windows command prompt, and
> manipulates excel with VBA.  Can you please tell me if this is correct?
> Likewise, can you please give me more information on how A.POI interfaces
> with windows.
> 
> I understand these questions are not short to answer.  If you have a
> website, blog, or book to recommend that would be a great start for me.
> 
> Thank you,
> 
> Sal.
> 
>  gn=sig-email&utm_content=webmail&utm_term=icon> Virus-free.
> www.avast.com
>  gn=sig-email&utm_content=webmail&utm_term=link>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>



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

Re: Booth Volunteers Needed for Open Source Summit Paris

[Hervé BOUTEMY]

I can be there on the 2 days, ready to help

Regards,

Hervé

Le vendredi 29 septembre 2017, 08:47:40 CEST Sharan Foga a écrit :
> Hi All
> 
> I am looking for volunteers to help out on the ASF booth for the Open Source
> Summit in Paris.
> 
> http://www.opensourcesummit.paris/
> 
> This conference is completely free and will be held on 6th and 7th December
> 2017.  If you are planning to attend the conference and want to spend some
> on the booth helping out or would like to use the booth for an hour or two
> to promote your Apache project then please let me know.
> 
> Please note that this is a mainly French speaking conference so it would be
> good to have some French speakers for this!
> 
> Thanks
> Sharan
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: Update to web site

[Hervé BOUTEMY]

done
thank you Craig

Hervé

Le lundi 18 septembre 2017, 10:15:25 CEST Craig Russell a écrit :
> Hi,
> 
> I made an update to the new committer guidelines at
> http://community.apache.org/newcommitter.html to clarify that after a
> successful vote, there should be a message with subject [RESULT][VOTE].
> 
> The update failed because of permissions.
> 
> Could someone on the PMC review the change and commit it if is is ok?
> http://community.staging.apache.org/newcommitter.html
> 
> Thanks,
> 
> Craig
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: French Language Help Needed re Paris Open Source Summit

[Hervé BOUTEMY]

Hi Sharan,

If a third one is useful, I can help also :)

Regards,

Hervé

Le lundi 18 septembre 2017, 21:42:37 CEST Jacques Le Roux a écrit :
> Hi Sharan,
> 
> I can at least help in translating the parts of the document you want.
> 
> Cheers
> 
> Jacques
> 
> Le 18/09/2017 à 14:45, Sharan Foga a écrit :
> > Hi All
> > 
> > I've contacted the organisers of the Open Source Summit  which is running
> > in Paris on 6th – 7th December 2017 to see if we can get a booth there
> > and possibly an Apache presentation track.
> > 
> > http://www.opensourcesummit.paris/
> > 
> > The organisers have sent me an instruction brochure (in French) so I need
> > the help of some francophones to understand it and co-ordinate the next
> > steps. There are some specific dates mentioned and I don't want to miss
> > any of the deadlines. So please let me know if you can help :-)
> > 
> > This is a free conference so is likely to attract a lot of visitors so
> > being there could be a good way to spread the Apache message.
> > 
> > Thanks
> > Sharan
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: committee-info.txt and projectName.rdf redundancy

[Hervé BOUTEMY]

the projectName.rdf is used by projects.a.o [1]: need to dig more into 
parsecommitteeinfo.py script to see which field is taken from .rdf and which 
one is from committee info

Regards,

Hervé

[1] https://svn.apache.org/repos/asf/comdev/projects.apache.org/scripts/
README.txt

Le lundi 28 août 2017, 09:40:49 CEST Jacques Le Roux a écrit :
> Thanks Hervé,
> 
> Actually the redundancy is in the content of the files. Both gives
> information about the PMC (mostly for the files in
> comdev\projects.apache.org\data\committees).
> 
> So you have to maintain both, but I understand why now.
> 
> The committee-info.txt serves as a reference. Do  you know if the
> projectName.rdf is used by an ASF mechanism, for a content integration
> somewhere?
> 
> Jacques
> 
> Le 27/08/2017 à 17:26, Hervé BOUTEMY a écrit :
> > Hi Jacques,
> > 
> > I don't really get what redundancy you're talking about (nor link with
> > cited commit, nor what discussion I had with Sebastian...)
> > 
> > One thing is that committee-info.txt is an ASF private resource where rdf
> > files are fully public. And RDF/DOAP files are supposed to give a full
> > model of everything for public share.
> > 
> > I was not at the beginning of DOAP deployment but just worked on the new
> > projects.a.o site, then I really have no idea on initial intends: I'm just
> > trying to guess like anybody else...
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le samedi 26 août 2017, 22:20:03 CEST Jacques Le Roux a écrit :
> >> Le 26/08/2017 à 21:58, Jacques Le Roux a écrit :
> >>> Le 26/08/2017 à 20:15, Jacques Le Roux a écrit :
> >>>> Hi,
> >>>> 
> >>>> Why is there a redundancy with committee-info.txt and projectName.rdf
> >>>> files at comdev\projects.apache.org\data\committees ?
> >>>> 
> >>>> Thanks
> >>>> 
> >>>> Jacques
> >>>> 
> >>>> 
> >>>> -
> >>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >>>> For additional commands, e-mail: dev-h...@community.apache.org
> >>> 
> >>> I mean about the PMC part in projectName.rdf of course
> >>> 
> >>> Jacques
> >>> 
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >>> For additional commands, e-mail: dev-h...@community.apache.org
> >> 
> >> OK this is related with http://svn.apache.org/r1691273
> >> and the discussion Hervé and Sebastian had (could not find it at
> >> https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:169127
> >> 3)
> >> 
> >> Ah forgot one point: committee-info.txt is maintained by chairs when
> >> projectName.rdf files are accessible to all committers (or PMC members,
> >> or
> >> ASF members? I'm all that, so not sure if others have the same accesses).
> >> 
> >> After reading the discussion between Hervé and Sebastian, the question
> >> still stands, why both?
> >> 
> >> Jacques
> >> 
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: committee-info.txt and projectName.rdf redundancy

[Hervé BOUTEMY]

Hi Jacques,

I don't really get what redundancy you're talking about (nor link with cited 
commit, nor what discussion I had with Sebastian...)

One thing is that committee-info.txt is an ASF private resource where rdf files 
are fully public. And RDF/DOAP files are supposed to give a full model of 
everything for public share.

I was not at the beginning of DOAP deployment but just worked on the new 
projects.a.o site, then I really have no idea on initial intends: I'm just 
trying to guess like anybody else...

Regards,

Hervé

Le samedi 26 août 2017, 22:20:03 CEST Jacques Le Roux a écrit :
> Le 26/08/2017 à 21:58, Jacques Le Roux a écrit :
> > Le 26/08/2017 à 20:15, Jacques Le Roux a écrit :
> >> Hi,
> >> 
> >> Why is there a redundancy with committee-info.txt and projectName.rdf
> >> files at comdev\projects.apache.org\data\committees ?
> >> 
> >> Thanks
> >> 
> >> Jacques
> >> 
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > I mean about the PMC part in projectName.rdf of course
> > 
> > Jacques
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> OK this is related with http://svn.apache.org/r1691273
> and the discussion Hervé and Sebastian had (could not find it at
> https://lists.apache.org/list.html?dev@community.apache.org:lte=3M:1691273)
> 
> Ah forgot one point: committee-info.txt is maintained by chairs when
> projectName.rdf files are accessible to all committers (or PMC members, or
> ASF members? I'm all that, so not sure if others have the same accesses).
> 
> After reading the discussion between Hervé and Sebastian, the question still
> stands, why both?
> 
> Jacques
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: Apache and Java

[Hervé BOUTEMY]

+1
just a little addition: "Java at Apache" was called Jakarta

I don't know if newbies know about Jakarta nowadays, but Jakarta was the home 
for so many tools that became later independant Apache Top Level Projects

Regards,

Hervé

Le dimanche 19 mars 2017, 17:03:09 CET Niclas Hedhman a écrit :
> I think it is a combination of several factors;
> 
>   * Historical - The first non-httpd project in Apache was Java, followed
> by a handful of others.
> 
>   * Java is one of the big languages.
> 
>   * Some projects are spin-offs from other ASF projects
> 
>   * External Java projects knows Apache Java projects very well, through
> Ant, Maven, Commons, Tomcat and many other they use. So if they seek a new
> home, ASF is one of the obvious choices. For C/C++, C#, Ruby and Python,
> this is not necessarily the case. There is often no natural tie between a
> random solo project in these languages and ASF.
> 
>   * The above is creating a reinforcement feedback loop, giving the
> impression that ASF is all about Java and perhaps overlooked for other
> platforms when seeking a new home.
> 
> 
> Hope that helps.
> Niclas
> 
> On Sun, Mar 19, 2017 at 4:27 PM, Spaghetti Roulette <
> 
> spaghettiroule...@mail.com> wrote:
> > Why do Apache projects use Java so extensively? It looks to me that a lot
> > of projects, if not most of them, are written in Java, and I can't get my
> > head around this fact. Is there any reason, perhaps technical, or is it
> > just coincidence?
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org



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

Re: OFBiz security team showing on security/projects.html ?

[Hervé BOUTEMY]

Hi,

Looks like this page is intended to point to your list.
This site can be edited through CMS by every members: I just did it, please 
review and eventually improve :)

Regards,

Hervé

Le dimanche 30 octobre 2016, 11:19:35 CET Jacques Le Roux a écrit :
> Hi,
> 
> We have now a secur...@ofbiz.apache.org 
> list, does it qualify to show on http://apache.org/security/projects.html ?
> If yes, am I able to do it myself?
> 
> Thanks
> 
> Jacques



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

Re: Adding some statistics to projects.a.o?

[Hervé BOUTEMY]

Le vendredi 28 octobre 2016, 10:41:37 CEST Daniel Gruno a écrit :
> > For Maven, the only option I see is pom.xml files: how can we confirm
> > this?
> > And confirm if language breakdowns counts files only, or weighted with
> > file size or with another weight?
> 
> It uses the same heuristics as CLoC (with a few modifications for
> increased stability), so you could run that locally and see why it does
> what it does.
ok, then here is the doc I'll add a pointer to
https://github.com/AlDanial/cloc#Languages

> language analysers are never 100% accurate, OpenHub's
> analyser is famous for making odd claims about Forth, and GitHub's
> downplays Python in many projects, the list goes on :)
> 
> Counts are lines of code, there is no weighting going on there. it's
> just raw figures.
> 
> > Is Snoot open sourced somewhere?
> 
> It's about as open as GitHub, OpenHub, Masterbranch etc :) The interface
> for the system is public and documented (under documentation/exports),
> but the internal systems on the boxes are proprietary for the most part.
great, all-sources is the API I needed to integrate content into projects.a.o 
build: we'll need to sort out which token to use, but at least I can start to 
work on interpreting results fetched by hand

https://api.snoot.io/api/3/api-docs#all-sources


> 
> With regards,
> Daniel.
> 
> > Regards,
> > 
> > Hervé
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: Adding some statistics to projects.a.o?

[Hervé BOUTEMY]

Le vendredi 28 octobre 2016, 10:27:31 CEST Daniel Gruno a écrit :
> > I have a snoot account, then I could have a look at the list of repos that
> > are taken into account. I have a few questions:
> > 1. can we show the list of repos from this statistics page?
> 
> Do you mean the entire list of repos analysed? I'm sure we could, I just
> don't quite know how we'd present it :) It's a rather large list.
yes, I mean the full list (740 repositories, Snoot says :) )
I know that making it appealing will require some work, but I think that it's 
important to make that information visible for people wanting to dig into 
these stats, and even help us fix issues on Snoot config

I'm even sure we could try to add this list of repos split by committee, on 
each committee page: that would make each PMC able to see its Snort config and 
once again help to fix issues

> 
> > 2. I saw that some imports are failing, because list of repos change over
> > time: how can I help fix issues?
> 
> If you're up for keeping the list updated, speak to Sally about getting
> admin privs on Snoot, I'm sure she'll be happy to have someone help out :)
great, I'll do, thanks

Regards,

Hervé

> 
> With regards,
> Daniel.
> 
> > Regards,
> > 
> > Hervé
> > 
> > [1] https://projects.apache.org/projects.html?pmc
> > 
> > Le mercredi 26 octobre 2016, 21:28:17 CEST Daniel Gruno a écrit :
> >> On 10/26/2016 09:06 PM, Mike Drob wrote:
> >>> A few section specific comments -
> >>> Largest/Busiest projects is difficult to make use of due to the huge
> >>> "other" section. Maybe a list makes more sense rather than a pie/circle
> >>> chart.Email, topics and email authors, past year -- more readable as a
> >>> line
> >>> chart and for a longer time span I think
> >> 
> >> Changing the email stats to lines was rather straightforward, so I've
> >> done that. I also changed it to just show stats for user/dev lists,
> >> leaving out the issues/commit lists which are rather chatty but not
> >> representative of email-based discussions. Changing the top repos by
> >> sloc/commits will require some time, as I'll have to write some custom
> >> representation for that.
> >> 
> >> With regards,
> >> Daniel.
> >> 
> >>> On Wed, Oct 26, 2016 at 1:07 PM, Daniel Gruno 
> > 
> > wrote:
>  I added an initial stats page at
>  https://projects.apache.org/statistics.html - assuming no one objects,
>  I'll add it to the top menu of the other pages in a day or so.
>  
>  Do peruse - anything we need to add/edit?
>  
>  With regards,
>  Daniel.
>  
>  On 10/26/2016 01:07 PM, Daniel Gruno wrote:
> > Hi folks,
> > I was wondering, since we have full access to Snoot for the ASF, why
> > not
> > take advantage of that and add a statistics page to
> > projects.apache.org,
> > showing the various live stats available (no. of commits/committers,
> > largest repos by size/commits, proper language breakdown, relationship
> > mapping, mail stats etc).
> > 
> > I was inclined to JFDI, but I'd love to hear what others think about
> > this. If I don't hear any loud objections, I'll add a stats page
> > today,
> > and we can see if it's of any use :)
> > 
> > Comments? Suggestions? :)
> > 
> > With regards,
> > Daniel.
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>  
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>  For additional commands, e-mail: dev-h...@community.apache.org
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: Adding some statistics to projects.a.o?

[Hervé BOUTEMY]

Le mercredi 26 octobre 2016, 23:12:44 CEST Daniel Gruno a écrit :
> On 10/26/2016 10:56 PM, Phil Steitz wrote:
> > On 10/26/16 11:07 AM, Daniel Gruno wrote:
> >> I added an initial stats page at
> >> https://projects.apache.org/statistics.html - assuming no one objects,
> >> I'll add it to the top menu of the other pages in a day or so.
> >> 
> >> Do peruse - anything we need to add/edit?
> > 
> > Maven is not a programming language.  What exactly is the
> > denominator on that stat?  Number of files?  Lines of code?
> > Projects primarily using?
> 
> I suspect it's scripts specifically for maven it's counting. the
> denominator is lines of functional code (101 million in total, not
> counting blanks and comments which take us to 150M total).
For Maven, the only option I see is pom.xml files: how can we confirm this?
And confirm if language breakdowns counts files only, or weighted with file 
size 
or with another weight?
Is Snoot open sourced somewhere?

Regards,

Hervé

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

Re: Adding some statistics to projects.a.o?

[Hervé BOUTEMY]

IIUC, this "Largest/Busiest projects" statistics is neither per project, 
neither per committee (or PMC), but per repo

notice: 1 committee (or PMC) = n projects [1]
and 1 committee may have many repos

I'll update the title to "Largest/Busiest repos", that will be less 
misleading.


I have a snoot account, then I could have a look at the list of repos that are 
taken into account. I have a few questions:
1. can we show the list of repos from this statistics page?
2. I saw that some imports are failing, because list of repos change over 
time: how can I help fix issues?

Regards,

Hervé

[1] https://projects.apache.org/projects.html?pmc

Le mercredi 26 octobre 2016, 21:28:17 CEST Daniel Gruno a écrit :
> On 10/26/2016 09:06 PM, Mike Drob wrote:
> > A few section specific comments -
> > Largest/Busiest projects is difficult to make use of due to the huge
> > "other" section. Maybe a list makes more sense rather than a pie/circle
> > chart.Email, topics and email authors, past year -- more readable as a
> > line
> > chart and for a longer time span I think
> 
> Changing the email stats to lines was rather straightforward, so I've
> done that. I also changed it to just show stats for user/dev lists,
> leaving out the issues/commit lists which are rather chatty but not
> representative of email-based discussions. Changing the top repos by
> sloc/commits will require some time, as I'll have to write some custom
> representation for that.
> 
> With regards,
> Daniel.
> 
> > On Wed, Oct 26, 2016 at 1:07 PM, Daniel Gruno  
wrote:
> >> I added an initial stats page at
> >> https://projects.apache.org/statistics.html - assuming no one objects,
> >> I'll add it to the top menu of the other pages in a day or so.
> >> 
> >> Do peruse - anything we need to add/edit?
> >> 
> >> With regards,
> >> Daniel.
> >> 
> >> On 10/26/2016 01:07 PM, Daniel Gruno wrote:
> >>> Hi folks,
> >>> I was wondering, since we have full access to Snoot for the ASF, why not
> >>> take advantage of that and add a statistics page to projects.apache.org,
> >>> showing the various live stats available (no. of commits/committers,
> >>> largest repos by size/commits, proper language breakdown, relationship
> >>> mapping, mail stats etc).
> >>> 
> >>> I was inclined to JFDI, but I'd love to hear what others think about
> >>> this. If I don't hear any loud objections, I'll add a stats page today,
> >>> and we can see if it's of any use :)
> >>> 
> >>> Comments? Suggestions? :)
> >>> 
> >>> With regards,
> >>> Daniel.
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >>> For additional commands, e-mail: dev-h...@community.apache.org
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



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

Re: Project references for Apache Fortress and Apache Kerby

[Hervé BOUTEMY]

yes, on next cron run (at 2AM UTC)

since we're on it, I just tested the parsing on my machine, to check: the new 
content was parsed without any issue

now let's the the magic happen with cron :)

Regards,

Hervé

Le samedi 12 décembre 2015 12:33:50 vous avez écrit :
> The process will pick up the corrected changes done to doap_fortress.rdf
> and doap_kerby.rdf automagically?
> 
> Best regards,
> 
> Pierre Smits
> 
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
> 
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
> 
> On Sat, Dec 12, 2015 at 11:18 AM, Hervé BOUTEMY 
> 
> wrote:
> > Hi Pierre,
> > 
> > I just launched parseprojects.py script on my machine to check and saw
> > that
> > your 2 new rdf are causing a parse failure.
> > This is caused by wrong asfext:pmc value:
> > http://directory.apache.org/team.html"; />
> > 
> > should be
> > http://directory.apache.org/"; />
> > 
> > like for apacheds [1]
> > 
> > It would be useful if the cronjob could send a message to the list when
> > such a
> > failure happens: don't know how to add this feature...
> > 
> > But at least for this time, fixing the rdf should to the job.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > 
> > [1]
> > http://svn.apache.org/repos/asf/directory/apacheds/trunk/doap_apacheds.rdf
> > 
> > Le samedi 12 décembre 2015 10:07:06 Pierre Smits a écrit :
> > > Hi all,
> > > 
> > > I have committed an adjustment to [1] to have the Fortress and Kerby
> > > projects of the Apache Directory project to have these visible in
> > > http://projects.apache.org. The changes are in, see [2], lines 145 and
> > 
> > 146.
> > 
> > > However, these changes don't show up in [3]. Did something go wrong?
> > > 
> > > 
> > > [1]
> > 
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/data/projects.xml
> > 
> > > [2]
> > 
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/data/projects.xml?
> > vi> 
> > > ew=markup&pathrev=1719235 [3]
> > > https://projects.apache.org/committee.html?directory
> > > 
> > > Best regards,
> > > 
> > > Pierre Smits
> > > 
> > > 
> > > 
> > > ORRTIZ.COM <http://www.orrtiz.com>
> > > OFBiz based solutions & services
> > > 
> > > OFBiz Extensions Marketplace
> > > http://oem.ofbizci.net/oci-2/

Re: Project references for Apache Fortress and Apache Kerby

[Hervé BOUTEMY]

Hi Pierre,

I just launched parseprojects.py script on my machine to check and saw that 
your 2 new rdf are causing a parse failure.
This is caused by wrong asfext:pmc value:
http://directory.apache.org/team.html"; />

should be
http://directory.apache.org/"; />

like for apacheds [1]

It would be useful if the cronjob could send a message to the list when such a 
failure happens: don't know how to add this feature...

But at least for this time, fixing the rdf should to the job.

Regards,

Hervé


[1] http://svn.apache.org/repos/asf/directory/apacheds/trunk/doap_apacheds.rdf

Le samedi 12 décembre 2015 10:07:06 Pierre Smits a écrit :
> Hi all,
> 
> I have committed an adjustment to [1] to have the Fortress and Kerby
> projects of the Apache Directory project to have these visible in
> http://projects.apache.org. The changes are in, see [2], lines 145 and 146.
> 
> However, these changes don't show up in [3]. Did something go wrong?
> 
> 
> [1]
> http://svn.apache.org/viewvc/comdev/projects.apache.org/data/projects.xml
> [2]
> http://svn.apache.org/viewvc/comdev/projects.apache.org/data/projects.xml?vi
> ew=markup&pathrev=1719235 [3]
> https://projects.apache.org/committee.html?directory
> 
> Best regards,
> 
> Pierre Smits
> 
> 
> 
> ORRTIZ.COM 
> OFBiz based solutions & services
> 
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/

Re: 答复: 答复: Forming a community of Apache fans in China - Apache China Community

[Hervé BOUTEMY]

ok, waiting for your feedback

but remember, stay really simple for the first try: we need to test the concept 
before trying to write much content, just an intro to our intent

Regards,

Hervé

Le jeudi 26 novembre 2015 12:54:23 Ted Liu a écrit :
> Thank Hervé for being committer and Luke & Lei for helping review. I'll
> provide a list of pages to be translated with priority and timeline for
> your feedbacks before moving on to work on them.
 
> Ted
> 
> -Original Message-
> From: Luke Han [mailto:luke...@gmail.com] 
> Sent: Thursday, November 26, 2015 5:43 PM
> To: dev@community.apache.org
> Subject: Re: 答复: 答复: Forming a community of Apache fans in China - Apache
> China Community
 
> There are many Chinese in ASF community who could help on this, We could
> engage them to help review.
 
> Count me as one:-)
> 
> Thanks.
> 
> Luke
> 
> 
> Best Regards!
> -
> 
> Luke Han
> 
> On Thu, Nov 26, 2015 at 4:56 PM, Lei Chang  wrote:
> 
> 
> > I can do the review.
> >
> >
> >
> > Cheers
> > Lei Chang
> >
> >
> >
> >
> > On Thu, Nov 26, 2015 at 2:43 PM, Hervé BOUTEMY 
> > wrote:
> >
> >
> >
> > > ok, I didn't catch you were not committer
> > >
> > >
> > >
> > > As Ross points out, you'll become committer after earning merit :) 
> > > and before that, you can provide content through CMS without being
> > > committer:
> > > did you try?
> > >
> > >
> > >
> > > I can play the committer role and try to get the content and commit 
> > > after you submitted it, to check that the process works: I just 
> > > won't be able to really review the content :) notice that I can 
> > > check what result I get using an automatic translation
> > > service: IMHO, this is part of the process that we should try
> > >
> > >
> > >
> > > Do we have a chinese speaking committer who could review the 
> > > content,
> > 
> > with
> > 
> > > Apache Way in mind to check that what is explained to chinese 
> > > speaking people regarding contribution is ok?
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > Hervé
> > >
> > >
> > >
> > > Le mercredi 25 novembre 2015 08:21:35 Ted Liu a écrit :
> > > 
> > > > Yes, that's what we are hoping for. I'd also like to become a 
> > > > committer
> > > 
> > > of
> > > 
> > > > comdev to review and to be able to edit the content.
> > >
> > >
> > >
> > > > Ted
> > > >
> > > >
> > > >
> > > > -Original Message-
> > > > From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> > > > Sent: Wednesday, November 25, 2015 3:56 PM
> > > > To: dev@community.apache.org
> > > > Subject: Re: 答复: 答复: Forming a community of Apache fans in China -
> > 
> > Apache
> > 
> > > > China Community
> > >
> > >
> > >
> > > > yes, that's what I meant: anybody can send patch, a committer must
> > 
> > commit
> > 
> > > >
> > > >
> > > > for me, "editing" was about publishing, ie requiring commit
> > > > privilege.
> > > >
> > > >
> > > >
> > > > but there is a feature I don't really master in CMS for 
> > > > non-committers
> > 
> > to
> > 
> > > > easily submit patches: I found the doc [1] but never tried it myself.
> > >  
> > >  This
> > >  
> > > > FAQ entry should probably be one of the first content to be 
> > > > translated
> > 
> > to
> > 
> > > > crowd-source translation :)
> > > > notice that if a currently non-committer propose a lot of good 
> > > > centent,
> > > 
> > > he
> > > 
> > > > could IMHO be  voted to be committer on comdev (ie not on any code 
> > > > TLP,
> > > 
> > > but
> > > 
> > > > general committer to have the commit bit to the site)
> > >
> > >
> > >
> > > > Regards,
> > > >
> > > >
> > > >
> > > > Hervé
> > > >
> > > >
> > > >
> > > > [1]
> > > >
&

Re: 答复: 答复: Forming a community of Apache fans in China - Apache China Community

[Hervé BOUTEMY]

ok, I didn't catch you were not committer

As Ross points out, you'll become committer after earning merit :)
and before that, you can provide content through CMS without being committer: 
did you try?

I can play the committer role and try to get the content and commit after you 
submitted it, to check that the process works: I just won't be able to really 
review the content :)
notice that I can check what result I get using an automatic translation 
service: IMHO, this is part of the process that we should try

Do we have a chinese speaking committer who could review the content, with 
Apache Way in mind to check that what is explained to chinese speaking people 
regarding contribution is ok?

Regards,

Hervé

Le mercredi 25 novembre 2015 08:21:35 Ted Liu a écrit :
> Yes, that's what we are hoping for. I'd also like to become a committer of
> comdev to review and to be able to edit the content. 
 
> Ted
> 
> -Original Message-
> From: Hervé BOUTEMY [mailto:herve.bout...@free.fr] 
> Sent: Wednesday, November 25, 2015 3:56 PM
> To: dev@community.apache.org
> Subject: Re: 答复: 答复: Forming a community of Apache fans in China - Apache
> China Community
 
> yes, that's what I meant: anybody can send patch, a committer must commit
> 
> for me, "editing" was about publishing, ie requiring commit privilege.
> 
> but there is a feature I don't really master in CMS for non-committers to
> easily submit patches: I found the doc [1] but never tried it myself.
 This
> FAQ entry should probably be one of the first content to be translated to
> crowd-source translation :) 
> notice that if a currently non-committer propose a lot of good centent, he
> could IMHO be  voted to be committer on comdev (ie not on any code TLP, but
> general committer to have the commit bit to the site)
 
> Regards,
> 
> Hervé
> 
> [1]
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.apache.
> org%2fdev%2fcmsref.html%23non-committer&data=01%7c01%7ctedl%40064d.mgd.micro
> soft.com%7c35910a4d30da427a867308d2f56de271%7c72f988bf86f141af91ab2d7cd011db
> 47%7c1&sdata=IuaGJ1X%2bE2ffXNN2d22Jcqg0T1mHUVtf8ey5BlCJoB0%3d
 
> Le mercredi 25 novembre 2015 01:15:31 Ted Liu a écrit :
> 
> > The site content is public. We can get the designated content 
> > translated, by crowdsourcing to the community volunteers here, then 
> > send to a Chinese committer to proofread and edit the site.
> 
>  
> 
> > 
> > Ted
> > 
> > 发件人: Hervé BOUTEMY<mailto:herve.bout...@free.fr>
> > 发送时间: ‎2015/‎11/‎25 8:38
> > 收件人: dev@community.apache.org<mailto:dev@community.apache.org>
> > 主题: Re: 答复: Forming a community of Apache fans in China - Apache China 
> > Community
> 
>  
> 
> > I don't exactly know what you mean by "crowd-source the tasks to the 
> > OSS community in China": currently, you must be Apache committer to be 
> > able to edit community site Then the first steps to engage people will 
> > have to come from existing chinese
> 
>  speaking committers: explaining non-committers how to send a patch
> 
> > would permit non-committers to help committers improve the content
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le samedi 21 novembre 2015 16:44:26 Ted Liu a écrit :
> > 
> > 
> > > I can help with these tasks since we, at KAIYUANSHE, have done the 
> > > similar to bring the great OSS governance and licensing content and 
> > > application from OSS-Watch in U.K. to our website by our 
> > > professional translators with Ross' guidance. One question, can we 
> > > crowd-source the tasks to the OSS community in China? Our KAIYUANSHE 
> > > members , including myself, can do translation and/or proofreading. 
> > > As said earlier, this would greatly inspire the communities and devs 
> > > here.
> > 
> > 
> > 
> > 
> > 
> > >
> > >
> > >
> > > Ted
> > > 
> > > 发件人: Hervé BOUTEMY<mailto:herve.bout...@free.fr>
> > > 发送时间: ‎2015/‎11/‎22 0:11
> > > 收件人: dev@community.apache.org<mailto:dev@community.apache.org>
> > > 主题: Re: Forming a community of Apache fans in China - Apache China 
> > > Community
> > 
> > 
> > 
> > 
> > 
> > > then IMHO some chinese speaking people should start writing a little 
> > > introduction on 
> > > https://na01.safelinks.protection.outlook.com/?url=community.apache.
> > > org&da
> > > t
> > > a=01%7c01%7ctedl%40064d.mgd.micr

Re: 答复: 答复: Forming a community of Apache fans in China - Apache China Community

[Hervé BOUTEMY]

yes, that's what I meant: anybody can send patch, a committer must commit

for me, "editing" was about publishing, ie requiring commit privilege.

but there is a feature I don't really master in CMS for non-committers to 
easily submit patches: I found the doc [1] but never tried it myself.
This FAQ entry should probably be one of the first content to be translated to 
crowd-source translation :)

notice that if a currently non-committer propose a lot of good centent, he 
could IMHO be  voted to be committer on comdev (ie not on any code TLP, but 
general committer to have the commit bit to the site)

Regards,

Hervé

[1] http://www.apache.org/dev/cmsref.html#non-committer

Le mercredi 25 novembre 2015 01:15:31 Ted Liu a écrit :
> The site content is public. We can get the designated content translated, by
> crowdsourcing to the community volunteers here, then send to a Chinese
> committer to proofread and edit the site.
 
> 
> Ted
> ________
> 发件人: Hervé BOUTEMY<mailto:herve.bout...@free.fr>
> 发送时间: ‎2015/‎11/‎25 8:38
> 收件人: dev@community.apache.org<mailto:dev@community.apache.org>
> 主题: Re: 答复: Forming a community of Apache fans in China - Apache China
> Community
 
> I don't exactly know what you mean by "crowd-source the tasks to the OSS
> community in China": currently, you must be Apache committer to be able to
> edit community site
> Then the first steps to engage people will have to come from existing
> chinese
 speaking committers: explaining non-committers how to send a patch
> would permit non-committers to help committers improve the content
> 
> Regards,
> 
> Hervé
> 
> Le samedi 21 novembre 2015 16:44:26 Ted Liu a écrit :
> 
> > I can help with these tasks since we, at KAIYUANSHE, have done the
> > similar
> > to bring the great OSS governance and licensing content and application
> > from OSS-Watch in U.K. to our website by our professional translators
> > with
> > Ross' guidance. One question, can we crowd-source the tasks to the OSS
> > community in China? Our KAIYUANSHE members , including myself, can do
> > translation and/or proofreading. As said earlier, this would greatly
> > inspire the communities and devs here.
> 
> 
> 
> >
> >
> > Ted
> > 
> > 发件人: Hervé BOUTEMY<mailto:herve.bout...@free.fr>
> > 发送时间: ‎2015/‎11/‎22 0:11
> > 收件人: dev@community.apache.org<mailto:dev@community.apache.org>
> > 主题: Re: Forming a community of Apache fans in China - Apache China
> > Community
> 
> 
> 
> > then IMHO some chinese speaking people should start writing a little
> > introduction on
> > https://na01.safelinks.protection.outlook.com/?url=community.apache.org&da
> > t
> > a=01%7c01%7ctedl%40064d.mgd.microsoft.com%7ca10fa05981994c5cfea308d2f28e6
> > a29
> > %7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=54Q9uFYNL%2b9O4ZG4zxpnXU2tF
> > s6I TD%2fXEQ4SICmtgME%3d, like newcomers [1], newbiefaq [2]
> 
> 
> 
> > IIRC, any ASF committer can edit the site
> >
> >
> >
> > once a few pages are available, then they could be referenced from
> > classical
> 
>  english site and we can work on creating a chinese-language
> 
> > mailing list
> > That's how I see the process, but I won't be able to do anything about
> > it,
> > since I don't speak chinese :)
> > (and I don't think there is such a strong need for a french equivalent)
> >
> >
> >
> > Regards,
> >
> >
> >
> > Hervé
> >
> >
> >
> > [1]
> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.
> > a
> > pache.org%2fnewcomers%2f&data=01%7c01%7ctedl%40064d.mgd.microsoft.com%7ca
> > 10f
> > a05981994c5cfea308d2f28e6a29%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata
> > =v0 8GdRcS%2f0tibOnuCAQiba8gjqhHj%2fDsd3A9e7uHATE%3d
> 
> 
> 
> > [2]
> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.
> > a
> > pache.org%2fnewbiefaq.html&data=01%7c01%7ctedl%40064d.mgd.microsoft.com%7
> > ca1
> > 0fa05981994c5cfea308d2f28e6a29%7c72f988bf86f141af91ab2d7cd011db47%7c1&sda
> > ta= kAkFbBrcS9HEDgsEraq1q14FGYjgOlcsqJcg39rwTdc%3d
> 
> 
> 
> > Le samedi 21 novembre 2015 13:53:03 Ted Liu a écrit :
> >
> >
> >
> > > Thank Niclas and Hervé, It is excited to see the great ideas to start
> > > with.
> 
>  If needed, we can help crowdsource for contributions in China and
> 
> > > it is very likely to excite and attract many 

Re: 答复: Forming a community of Apache fans in China - Apache China Community

[Hervé BOUTEMY]

I don't exactly know what you mean by "crowd-source the tasks to the OSS 
community in China": currently, you must be Apache committer to be able to 
edit community site
Then the first steps to engage people will have to come from existing chinese 
speaking committers: explaining non-committers how to send a patch would 
permit non-committers to help committers improve the content

Regards,

Hervé

Le samedi 21 novembre 2015 16:44:26 Ted Liu a écrit :
> I can help with these tasks since we, at KAIYUANSHE, have done the similar
> to bring the great OSS governance and licensing content and application
> from OSS-Watch in U.K. to our website by our professional translators with
> Ross' guidance. One question, can we crowd-source the tasks to the OSS
> community in China? Our KAIYUANSHE members , including myself, can do
> translation and/or proofreading. As said earlier, this would greatly
> inspire the communities and devs here.
 
> 
> Ted
> ____
> 发件人: Hervé BOUTEMY<mailto:herve.bout...@free.fr>
> 发送时间: ‎2015/‎11/‎22 0:11
> 收件人: dev@community.apache.org<mailto:dev@community.apache.org>
> 主题: Re: Forming a community of Apache fans in China - Apache China
> Community
 
> then IMHO some chinese speaking people should start writing a little
> introduction on
> https://na01.safelinks.protection.outlook.com/?url=community.apache.org&dat
> a=01%7c01%7ctedl%40064d.mgd.microsoft.com%7ca10fa05981994c5cfea308d2f28e6a29
> %7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=54Q9uFYNL%2b9O4ZG4zxpnXU2tFs6I
> TD%2fXEQ4SICmtgME%3d, like newcomers [1], newbiefaq [2]
 
> IIRC, any ASF committer can edit the site
> 
> once a few pages are available, then they could be referenced from
> classical
 english site and we can work on creating a chinese-language
> mailing list 
> That's how I see the process, but I won't be able to do anything about it,
> since I don't speak chinese :)
> (and I don't think there is such a strong need for a french equivalent)
> 
> Regards,
> 
> Hervé
> 
> [1]
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.a
> pache.org%2fnewcomers%2f&data=01%7c01%7ctedl%40064d.mgd.microsoft.com%7ca10f
> a05981994c5cfea308d2f28e6a29%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=v0
> 8GdRcS%2f0tibOnuCAQiba8gjqhHj%2fDsd3A9e7uHATE%3d
 
> [2]
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.a
> pache.org%2fnewbiefaq.html&data=01%7c01%7ctedl%40064d.mgd.microsoft.com%7ca1
> 0fa05981994c5cfea308d2f28e6a29%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=
> kAkFbBrcS9HEDgsEraq1q14FGYjgOlcsqJcg39rwTdc%3d
 
> Le samedi 21 novembre 2015 13:53:03 Ted Liu a écrit :
> 
> > Thank Niclas and Hervé, It is excited to see the great ideas to start
> > with.
 If needed, we can help crowdsource for contributions in China and
> > it is very likely to excite and attract many talented young people to
> > contribute.>
> >
> 
> 
> 
> > Other than the great content, email list, webpage, etc., we can also help
> > from user experience side, such as pages in Chinese for mobile or a
> > Wechat
> > public account for news, blogs publishing or other services, and social
> > interactions thru Wechat or QQ, such as allowing any Chinese Apache fans
> > to
 retweet and socialize great articles.
> 
> 
> 
> > p.s. The reason why a Wechat public account is a big plus because it is
> > used
 by 500M Wechat chatters on daily basis to acquire/learn
> > information. This is a very effective China-specific scenario.
> 
> 
> 
> >
> >
> > -Original Message-
> > From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> > Sent: Saturday, November 21, 2015 7:56 PM
> > To: dev@community.apache.org
> > Subject: Re: Forming a community of Apache fans in China - Apache China
> > Community
> 
> 
> 
> > thinking more about it
> >
> >
> >
> > Imagine:
> > - a few localized pages in
> > https://na01.safelinks.protection.outlook.com/?url=community.apache.org&da
> > t
> > a=01%7c01%7ctedl%40064d.mgd.microsoft.com%7c3739535c7a0d4f23100108d2f26ac
> > 9d7
> > %7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2fZti2MXsNqqO0quW2NRyF45mp
> > fx7 pTE14aitDzC3nVk%3d about tooling, culture and so on + mailing list to
> > interact
> 
>  - as a first step, previous localized team could provide a little
> 
> > localized page to  each classical TLP (managed primarily in english) to
> > explain the purpose of the TLP and how they can contact localized
> > https://na01.safelinks.protection.outlook.com/?url

Re: Forming a community of Apache fans in China - Apache China Community

[Hervé BOUTEMY]

then IMHO some chinese speaking people should start writing a little 
introduction on community.apache.org, like newcomers [1], newbiefaq [2]

IIRC, any ASF committer can edit the site

once a few pages are available, then they could be referenced from classical 
english site and we can work on creating a chinese-language mailing list

That's how I see the process, but I won't be able to do anything about it, 
since I don't speak chinese :)
(and I don't think there is such a strong need for a french equivalent)

Regards,

Hervé

[1] http://community.apache.org/newcomers/

[2] http://community.apache.org/newbiefaq.html

Le samedi 21 novembre 2015 13:53:03 Ted Liu a écrit :
> Thank Niclas and Hervé, It is excited to see the great ideas to start with.
> If needed, we can help crowdsource for contributions in China and it is
> very likely to excite and attract many talented young people to contribute.
> 
 
> Other than the great content, email list, webpage, etc., we can also help
> from user experience side, such as pages in Chinese for mobile or a Wechat
> public account for news, blogs publishing or other services, and social
> interactions thru Wechat or QQ, such as allowing any Chinese Apache fans to
> retweet and socialize great articles. 
 
> p.s. The reason why a Wechat public account is a big plus because it is used
> by 500M Wechat chatters on daily basis to acquire/learn information. This
> is a very effective China-specific scenario.
 
> 
> -Original Message-
> From: Hervé BOUTEMY [mailto:herve.bout...@free.fr] 
> Sent: Saturday, November 21, 2015 7:56 PM
> To: dev@community.apache.org
> Subject: Re: Forming a community of Apache fans in China - Apache China
> Community
 
> thinking more about it
> 
> Imagine:
> - a few localized pages in
> https://na01.safelinks.protection.outlook.com/?url=community.apache.org&dat
> a=01%7c01%7ctedl%40064d.mgd.microsoft.com%7c3739535c7a0d4f23100108d2f26ac9d7
> %7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2fZti2MXsNqqO0quW2NRyF45mpfx7
> pTE14aitDzC3nVk%3d about tooling, culture and so on + mailing list to
> interact
 - as a first step, previous localized team could provide a little
> localized page to  each classical TLP (managed primarily in english) to
> explain the purpose of the TLP and how they can contact localized
> https://na01.safelinks.protection.outlook.com/?url=community.apache.org&dat
> a=01%7c01%7ctedl%40064d.mgd.microsoft.com%7c3739535c7a0d4f23100108d2f26ac9d7
> %7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2fZti2MXsNqqO0quW2NRyF45mpfx7
> pTE14aitDzC3nVk%3d to get help to interact with the TLP 
> IMHO, it's not about translating everything in every TLP: it's about putting
> in every TLP  (starting with
> https://na01.safelinks.protection.outlook.com/?url=www.apache.org&data=01%7
> c01%7ctedl%40064d.mgd.microsoft.com%7c3739535c7a0d4f23100108d2f26ac9d7%7c72f
> 988bf86f141af91ab2d7cd011db47%7c1&sdata=1owk036Iz0L7CvCjYK79VJYn0zU%2fKsXoeT
> kFfi3ED5k%3d and
> https://na01.safelinks.protection.outlook.com/?url=incubator.apache.org&dat
> a=01%7c01%7ctedl%40064d.mgd.microsoft.com%7c3739535c7a0d4f23100108d2f26ac9d7
> %7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZvN%2ftVv2eINlLZHjEmc7jGf7xoXS
> RA6MXUtczeSshXk%3d) a localized pointer to localized helpers in
> community.apache.org.
 
> Of course, if the localized team grows big, they can engage more
> translations on some TLPs.
 
> Then +1 to creating ch...@community.apache.org +
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.a
> pache.org%2fchina.html&data=01%7c01%7ctedl%40064d.mgd.microsoft.com%7c373953
> 5c7a0d4f23100108d2f26ac9d7%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=OlA9
> hXKy5wFT2z%2fPNWm%2f%2fRl%2bLcCLvKxI7DwDoZVYvsE%3d to explain the concept
> And probably
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.a
> pache.org%2finternational.html&data=01%7c01%7ctedl%40064d.mgd.microsoft.com%
> 7c3739535c7a0d4f23100108d2f26ac9d7%7c72f988bf86f141af91ab2d7cd011db47%7c1&sd
> ata=o%2bhr%2b0B77v2nXFdQsAoby8ISqKHYky4i5Sluma9ViyE%3d to point to every
> localization where this process is started
 
> Notice: instead of "china" = a country name in english, we should name it
> after language: ISO-639 alpha-3 codes seem a better choice
 
> IMHO, easy to start and see which locales get traction
> 
> Regards,
> 
> Hervé
> 
> Le samedi 21 novembre 2015 19:34:11 Niclas Hedhman a écrit :
> 
> > I agree that translated content is a great start, if there is enough 
> > energy for it.
> > 
> > There are three main "entry points" into Apache outside of the 
> > projects themselves;
> > 
> >   a.
> >   https://na01

Re: Forming a community of Apache fans in China - Apache China Community

[Hervé BOUTEMY]

thinking more about it

Imagine:
- a few localized pages in community.apache.org about tooling, culture and so 
on + mailing list to interact
- as a first step, previous localized team could provide a little localized 
page to  each classical TLP (managed primarily in english) to explain the 
purpose of the TLP and how they can contact localized community.apache.org to 
get help to interact with the TLP

IMHO, it's not about translating everything in every TLP: it's about putting 
in every TLP  (starting with www.apache.org and incubator.apache.org) a 
localized pointer to localized helpers in community.apache.org.

Of course, if the localized team grows big, they can engage more translations 
on some TLPs.

Then +1 to creating ch...@community.apache.org + 
http://community.apache.org/china.html to explain the concept
And probably http://community.apache.org/international.html to point to every 
localization where this process is started

Notice: instead of "china" = a country name in english, we should name it 
after language: ISO-639 alpha-3 codes seem a better choice

IMHO, easy to start and see which locales get traction

Regards,

Hervé

Le samedi 21 novembre 2015 19:34:11 Niclas Hedhman a écrit :
> I agree that translated content is a great start, if there is enough energy
> for it.
> 
> There are three main "entry points" into Apache outside of the projects
> themselves;
>   a. www.apache.org
>   b. incubator.apache.org
>   c. community.apache.org
> 
> As far as I know, the actual content is in some markdown text format, and
> should be relatively easy to get going page by page, and I am sure
> Infrastructure will be able to let us know where to put it, and link it
> into the user experience "somehow".
> 
> That content alone are probably volunteer-months worth of work, especially
> since I think peer review is very important, since language matters for
> policy and such.
> 
> *I* am also very positive to alternate language community.apache.org
> mailing lists. ch...@community.apache.org could be a start, and from there
> it should be possible to gauge the interest.
> 
> For the rest of ComDev; I was added to the WeChat (a Chinese WhatsApp-like
> app) group that is now 360 people. If the chatter there could be directed
> to ch...@community.apache.org, we would possibly have a semi-busy list from
> the start.
> 
> 
> Niclas
> 
> On Sat, Nov 21, 2015 at 7:15 PM, Ted Liu  wrote:
> > Yes, agreed. We can help motivate people, maybe crowdsourcing, here to
> > help translate. But need to consider what contents and a streamline user
> > experience.  Ted
> > 
> > -Original Message-
> > From: Ross Gardler [mailto:ross.gard...@microsoft.com]
> > Sent: Saturday, November 21, 2015 7:00 PM
> > To: dev@community.apache.org
> > Subject: RE: Forming a community of Apache fans in China - Apache China
> > Community
> > 
> > Localized content is a great suggestion.
> > 
> > -Original Message-
> > From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
> > Sent: Saturday, November 21, 2015 2:58 AM
> > To: dev@community.apache.org
> > Subject: Re: Forming a community of Apache fans in China - Apache China
> > Community
> > 
> > I like the idea of doing something to better engage with China or India or
> > "country of your choice" people interested in Open Source but not able
> > currently because of language and cultural barriers for masses
> > 
> > But when I read "forming the Apache China Community", I read forming
> > something completely separate, and eventually forming a separate TLP:
> > staying short, I'm not convinced
> > 
> > What about creating localized content in
> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.
> > apache.org%2f&data=01%7c01%7cRoss.Gardler%40microsoft.com%7c3f189780a87344
> > cabc1608d2f262b677%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=1RvsCGO3%2
> > fEVJ6QXQEt%2bBcV%2bVlrhqAXHD1jAPYGjUZ6w%3d , pointing to dedicated
> > non-english language mailing lists, focused on explaining community
> > aspects, how to engage with Apache projects and to deal with the fact
> > that Apache projects are done in english?
> > 
> > Because I don't see:
> > - how we could do localized lists for every Apache TLP
> > - how we could do a TLP that we can't interact with in english (I can say
> > it because I'm not native english: english language is our minimum common
> > convention, and it cost me to learn it :) )
> > 
> > But perhaps existing community TLP could have localized sub-projects
> > (taking the form of content + m

Re: Forming a community of Apache fans in China - Apache China Community

[Hervé BOUTEMY]

I like the idea of doing something to better engage with China or India or 
"country of your choice" people interested in Open Source but not able 
currently because of language and cultural barriers for masses

But when I read "forming the Apache China Community", I read forming something 
completely separate, and eventually forming a separate TLP: staying short, I'm 
not convinced

What about creating localized content in http://community.apache.org/ , 
pointing to dedicated non-english language mailing lists, focused on 
explaining community aspects, how to engage with Apache projects and to deal 
with the fact that Apache projects are done in english?

Because I don't see:
- how we could do localized lists for every Apache TLP
- how we could do a TLP that we can't interact with in english (I can say it 
because I'm not native english: english language is our minimum common 
convention, and it cost me to learn it :) )

But perhaps existing community TLP could have localized sub-projects (taking 
the form of content + mailing lists, but not code) targeted at helping people 
work with other TLPs

WDYT?

Regards,

Hervé

Le samedi 21 novembre 2015 18:14:11 Ted Dunning a écrit :
> Ted,
> 
> It is not clear that what you want to happen is not happening.
> 
> There does seem to be an open discussion. Here and elsewhere.
> 
> What exactly do you want to happen?
> 
> What good thing is not happening?
> 
> What bad thing is happening?
> 
> Sent from my iPhone
> 
> > On Nov 21, 2015, at 17:58, Ted Liu  wrote:
> > 
> > Hi Niclas,
> > 
> > It'd be appreciated an open and constructive discussion can be formed at
> > ASF instead of labeling or stereotyping. The ask of forming of a
> > community, group or alike in China comes from the grass-root idea and
> > action because there are strong demands here. Otherwise nobody would care
> > and nobody could be instructed or directed. That’s the reason why a group
> > of Chinese ASF members, PMC members, committers, contributors, etc., want
> > to work together voluntarily to change the status quo by bridging the
> > Chinese talents and good projects to/from ASF. The motivation and
> > enablement of the local community/group will be mainly from the
> > experienced Chinese ASF members, committers and contributors, who people
> > will trust, instead of any individual new to ASF.
> > 
> > Talking about the language barrier, you should already know how difficult
> > it is to learn Chinese after living 4+ years in Shanghai. One recent
> > example is that literally no one from the Apache Fans Wechat social group
> > (360 people now) responded to your proposal, in English, to hold a
> > technical meetup in Shanghai. Your ASF status and the fact of your
> > location in Shanghai do not automatically translate into trust and
> > effective communication to enable and motivate people's actions. The wait
> > of a good machine translation is an unknown that younger generation
> > contributors would not tolerate.
> > 
> > The more challenging part is the culture differences where the sense of
> > community, governance, contribution and the Apache Way are still at
> > infant stage in China. There are more than enough good codes and events
> > (conferences, meetups, etc.) in China. The real blockers are language and
> > non-Apache-Way culture where the proposed China community/group can
> > contribute.
> > 
> > 
> > Ted
> > 
> > -Original Message-
> > From: Niclas Hedhman [mailto:hedh...@gmail.com]
> > Sent: Saturday, November 21, 2015 3:02 PM
> > To: dev@community.apache.org
> > Subject: Re: Forming a community of Apache fans in China - Apache China
> > Community
> > 
> > Ted,
> > 2 things...
> > 
> > 1. There were Apache Roadshows in Shanghai in 2010 and 2011.
> > 
> > 2. I am glad to see your enthusiasm of forming/creating organization. But
> > the ASF and many other open source projects are not command&control
> > driven top-down structures. So, there is very little "need" for "creation
> > of communities". They either form, or they don't.
> > 
> > I was happy to see that the younger generation at the Roadshow in Beijing
> > grasped that idea very well, whereas the somewhat older generation had a
> > more top-down approach, of wanting to build it like a company, like a
> > government or a religious organization. I hope that you can appreciate
> > the difference and channel your enthusiasm slightly differently.
> > 
> > Like you, I think language barrier is currently a big barrier, but I have
> > first hand witnessed the improvements in online translation services in
> > the past few years. Enormous improvement. Perhaps we are soon at a stage
> > where this can be an additional tool to bridge this gap.
> > 
> > My suggestions are towards localized meetups, where discussion, hacking,
> > presentations are conducted, by the participants, for the participants, a
> > peer-to-peer environment. Apache doesn't need to be formally involved in
> > this, but I am sure many Apache contributo

Re: [reporter] Confusing PMC/Committeer/Committee/LDAP report format

[Hervé BOUTEMY]

ok, if you stay only on PMC composition information, please just remove the 
LDAP part: this only adds confusion

adding another section is useful if it's about another information: I thought 
information about count of committers was useful (even if not always easy to 
know which are the few TLPs who let every ASF committer commit)

Regards,

Hervé

Le lundi 19 octobre 2015 01:22:37 sebb a écrit :
> On 19 October 2015 at 00:44, Hervé BOUTEMY  wrote:
> >> -- cut here --
> >> 
> >> ## PMC changes:
> >>  - Currently 42 PMC members listed in committee-info.txt.
> >>  - No new PMC members added in the last 3 months
> >>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> >> 
> >> ## LDAP unix group changes:
> >>  - Currently 44 members
> >>  - Radu Manole was added on Tue Oct 06 2015
> >> 
> >> -- cut here --
> >> 
> >> Would that satisfy everyone?
> > 
> > IMHO, making explicit which "LDAP unix group" is looked at would be useful
> 
> There is only one LDAP unix group for each PMC.
> 
> > Since I still don't understand if it's the committers group or PMC group
> > (I expect it to be the committers group)
> 
> The committers group maintained using modify_unix_group.pl
> 
> The committee group is maintained using modify_committee.pl
> 
> > and if oodt-pmc LDAP does not have the same count as PMC members listed in
> > committee-info.txt, a warning should be added in the first section
> 
> Such a warning does not belong in the report to the board, so does not
> belong in the report template.
> It might be worth adding a warning to the previous LDAP section.
> 
> > Regards,
> > 
> > Hervé
> > 
> > Le dimanche 18 octobre 2015 14:19:00 sebb a écrit :
> >> The app currently says for OODT:
> >> 
> >> -- cut here --
> >> 
> >> ## PMC changes:
> >>  - Currently 42 PMC members.
> >>  - No new PMC members added in the last 3 months
> >>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> >>  
> >>  
> >>  - Currently 44 committers and 43 PMC members.
> >>  - Radu Manole was added to the PMC on Sun Oct 11 2015
> >>  - Radu Manole was added as a committer on Tue Oct 06 2015
> >> 
> >> -- cut here --
> >> 
> >> Note that there are either 42 or 43 PMC members. (*)
> >> I think the above is a lot more confusing than the previous version which
> >> was:
> >> 
> >> -- cut here --
> >> 
> >> ## PMC changes:
> >>  - Currently 42 PMC members.
> >>  - No new PMC members added in the last 3 months
> >>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> >> 
> >> ## LDAP changes:
> >>  - Currently 44 committers and 43 committee group members.
> >>  - Radu Manole was added to the committee group on Sun Oct 11 2015
> >>  - Radu Manole was added as a committer on Tue Oct 06 2015
> >> 
> >> -- cut here --
> >> 
> >> As I already wrote, there is now no reason for the LDAP committee
> >> changes to be listed in the board report.
> >> 
> >> So what I propose is:
> >> 
> >> -- cut here --
> >> 
> >> ## PMC changes:
> >>  - Currently 42 PMC members listed in committee-info.txt.
> >>  - No new PMC members added in the last 3 months
> >>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> >> 
> >> ## LDAP unix group changes:
> >>  - Currently 44 members
> >>  - Radu Manole was added on Tue Oct 06 2015
> >> 
> >> -- cut here --
> >> 
> >> Would that satisfy everyone?
> >> 
> >> (*) that is because Radu has not yet been added to committee-info.txt
> >> so is not yet officially a member of the PMC
> >> 
> >> On 18 October 2015 at 10:12, sebb  wrote:
> >> > On 18 October 2015 at 09:31, Hervé BOUTEMY  
wrote:
> >> >> from my understanding:
> >> >> - PMC composition is available in 2 forms: committee-info.txt (=
> >> >> golden
> >> >> source) and LDAP xxx-pmc group
> >> > 
> >> > The *only* record of current PMC membership is committee-info.txt.
> >> > 
> >> > The LDAP committee group (modify_committee.pl) is only used for
> >> > granting karma, e.g. to PMC-private SVN and dist/release.
> 

Re: [reporter] Confusing PMC/Committeer/Committee/LDAP report format

[Hervé BOUTEMY]

> -- cut here --
> ## PMC changes:
> 
>  - Currently 42 PMC members listed in committee-info.txt.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> 
> ## LDAP unix group changes:
> 
>  - Currently 44 members
>  - Radu Manole was added on Tue Oct 06 2015
> -- cut here --
> 
> Would that satisfy everyone?
IMHO, making explicit which "LDAP unix group" is looked at would be useful
Since I still don't understand if it's the committers group or PMC group
(I expect it to be the committers group)

and if oodt-pmc LDAP does not have the same count as PMC members listed in 
committee-info.txt, a warning should be added in the first section

Regards,

Hervé

Le dimanche 18 octobre 2015 14:19:00 sebb a écrit :
> The app currently says for OODT:
> 
> -- cut here --
> ## PMC changes:
> 
>  - Currently 42 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> 
> 
>  - Currently 44 committers and 43 PMC members.
>  - Radu Manole was added to the PMC on Sun Oct 11 2015
>  - Radu Manole was added as a committer on Tue Oct 06 2015
> -- cut here --
> 
> Note that there are either 42 or 43 PMC members. (*)
> I think the above is a lot more confusing than the previous version which
> was:
> 
> -- cut here --
> ## PMC changes:
> 
>  - Currently 42 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> 
> ## LDAP changes:
> 
>  - Currently 44 committers and 43 committee group members.
>  - Radu Manole was added to the committee group on Sun Oct 11 2015
>  - Radu Manole was added as a committer on Tue Oct 06 2015
> -- cut here --
> 
> As I already wrote, there is now no reason for the LDAP committee
> changes to be listed in the board report.
> 
> So what I propose is:
> 
> -- cut here --
> ## PMC changes:
> 
>  - Currently 42 PMC members listed in committee-info.txt.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Dana Freeborn at Fri Mar 27 2015
> 
> ## LDAP unix group changes:
> 
>  - Currently 44 members
>  - Radu Manole was added on Tue Oct 06 2015
> -- cut here --
> 
> Would that satisfy everyone?
> 
> (*) that is because Radu has not yet been added to committee-info.txt
> so is not yet officially a member of the PMC
> 
> On 18 October 2015 at 10:12, sebb  wrote:
> > On 18 October 2015 at 09:31, Hervé BOUTEMY  wrote:
> >> from my understanding:
> >> - PMC composition is available in 2 forms: committee-info.txt (= golden
> >> source) and LDAP xxx-pmc group
> > 
> > The *only* record of current PMC membership is committee-info.txt.
> > 
> > The LDAP committee group (modify_committee.pl) is only used for
> > granting karma, e.g. to PMC-private SVN and dist/release.
> > 
> > They should generally have the same members, since all (and perhaps
> > only) PMC members should have the karma.
> > 
> > However this is not always the case, and it's important not to confuse the
> > two.> 
> >> - committers list is available only in LDAP as xxx group
> > 
> > The LDAP unix group (modify_unix_group.pl) generally grants karma to SVN.
> > However not every PMC uses it - e.g. Commons and Subversion allow any
> > ASF committer to commit.
> > 
> >> then instead of displaying:
> >> * PMC from committee-info
> >> * LDAP info: PMC + committers
> >> 
> >> it would be easier to understand if the structure was more:
> >> * PMC info from committee-info (and warning if LDAP PMC info is not
> >> consistent)
> > 
> > The consistency check is already done by Whimsy, but I suppose it
> > could be repeated here.
> > Or the Whimsy page could be linked if there was a discrepancy.
> > 
> >> * committers info (no need to explain that it comes from LDAP)
> >> 
> >> WDYT?
> > 
> > That is basically what it did say before the recent change.
> > 
> > Except that I do think it's necessary to explain that the committer
> > (modify_unix_group.pl) info is just an LDAP group.
> > 
> > There is no direct relationship with committers on a project in general.
> > Commons and Subversion don't use the group for commit karma.
> > Also it's relatively rare that people are dropped from the unix group,
> > even if they have stopped contributing.
> > S

Re: [reporter] Confusing PMC/Committeer/Committee/LDAP report format

[Hervé BOUTEMY]

from my understanding:
- PMC composition is available in 2 forms: committee-info.txt (= golden 
source) and LDAP xxx-pmc group
- committers list is available only in LDAP as xxx group


then instead of displaying:
* PMC from committee-info
* LDAP info: PMC + committers

it would be easier to understand if the structure was more:
* PMC info from committee-info (and warning if LDAP PMC info is not 
consistent)
* committers info (no need to explain that it comes from LDAP)


WDYT?

Hervé

Le vendredi 16 octobre 2015 23:24:16 sebb a écrit :
> On 16 October 2015 at 21:08, Pierre Smits  wrote:
> > I feel confident that anybody objects to ambiguous information, and that
> > no
> > one will object to improvement.
> 
> I do object to conflating LDAP committee and PMC membership.
> The two are completely distinct (although related).
> 
> This is why I changed the text to show LDAP committee rather than PMC
> a while back.
> At the time, the tool did not analyse the actual PMC membership, only LDAP.
> 
> However it does now, so the output shows them as distinct items.
> 
> The LDAP committee information is not really relevant to the board, so
> could now be dropped from the report skeleton.
> 
> But I think it is completely wrong to imply that changes to the LDAP
> committee group have any bearing on PMC membership.
> 
> > Best regards,
> > 
> > Pierre Smits
> > 
> > *OFBiz Extensions Marketplace*
> > http://oem.ofbizci.net/oci-2/
> > 
> > On Fri, Oct 16, 2015 at 8:20 PM, Rich Bowen  wrote:
> >> Although I acknowledge that the LDAP membership and the project
> >> membership
> >> might be different in certain weird edge cases, for the purpose of
> >> actually
> >> generating a board report, I find the current formatting confuses me
> >> Every
> >> Single Time.
> >> 
> >> Viz:
> >> 
> >> ## PMC changes:
> >>  - Currently 10 PMC members.
> >>  - No new PMC members added in the last 3 months
> >>  - Last PMC addition was Jean-Fran=C3=A7ois Maury at Mon Apr 07 2014
> >> 
> >> ## LDAP changes:
> >>  - Currently 26 committers and 10 committee group members.
> >>  - No new committee group members added in the last 3 months
> >>  - No new committers added in the last 3 months
> >>  - Last committer addition was Lyor Goldstein at Thu Apr 30 2015
> >> 
> >> So, I can tease out of that there's 26 committers, and 10 PMC members,
> >> and
> >> the latest additions were Jean Francois on April 7, and Lyor on April 30.
> >> The rest of that phrasing is confusing to me. committee vs committer and
> >> LDAP vs ... whatever. Not sure.
> >> 
> >> Does anybody object to me reformatting this a little, so that it won't
> >> confuse me next month?
> >> 
> >> --Rich
> >> 
> >> 
> >> --
> >> Rich Bowen - rbo...@rcbowen.com - @rbowen
> >> http://apachecon.com/ - @apachecon

Re: projects.apache.org/project.html

[Hervé BOUTEMY]

Hi Karl Heinz,

For projects.a.o
https://projects.apache.org/project.html?maven lists data from rdf

The issue is in rdf file, not the display :)

Regards,

Hervé

Le vendredi 25 septembre 2015 22:08:43 Karl Heinz Marbaise a écrit :
> Hi to all,
> 
> I have two things:
> 
> First:
> 
> If i take a look on the page:
> https://projects.apache.org/project.html?maven
> 
> i can't see any release which has been made in 2015...
> 
> If i take a look here:
> https://reporter.apache.org/addrelease.html?maven
> i can see that Maven 3.3.1 and Maven 3.3.3 had been released in 2015...
> 
> 
> Second:
> 
> Typo on page
>   https://reporter.apache.org/addrelease.html?maven
> There is a wrong entry in the above overview..
> 
> The culprit is:
> - maven-assembly-plugin-2.54: Mon Apr 27 2015
> 
> which needed to be changed into:
> - maven-assembly-plugin-2.5.4: Mon Apr 27 2015
> 
> 
> First how can this be changed ?
> 
> Furthermore i would like to know why such projects
> (https://reporter.apache.org/addrelease.html)...does not have a issue
> tracker (via JIRA) in ASF ?
> 
> Kind regards
> Karl Heinz Marbaise

Re: Unnecessary SVN commits [was: svn commit: r1691273 - in /comdev/projects.apache.org/site: doap/cxf/cxf.rdf doap/httpd/httpd.rdf json/foundation/projects.json json/projects/cxf.json json/projects/h

[Hervé BOUTEMY]

Le mercredi 22 juillet 2015 00:16:40 sebb a écrit :
> On 21 July 2015 at 06:45, Hervé BOUTEMY  wrote:
> > Le lundi 20 juillet 2015 01:43:11 sebb a écrit :
> >> On 19 July 2015 at 14:18, Hervé BOUTEMY  wrote:
> >> > time to explain what I have in mind, because I understand the reactions
> >> > about these svn content questions: but I need to explain why I think
> >> > that
> >> > it's not a bug, it's a feature :)
> >> > 
> >> > 
> >> > 1. generated json files in svn
> >> > 
> >> > even if they are generated, these ones are IMHO useful to ease people
> >> > just
> >> > wanting to work on information rendering, ie the site's html+javascript
> >> 
> >> The current files can still be accessed from the web server; they
> >> don't have to be in SVN to be useful.
> > 
> > seems I was not clear: the question is not the web server.
> > The question is the lambda ASF committer who does not have access to the
> > web server but would like to contribute to the web part, fix an issue he
> > sees on the live site: currently, one svn checkout, read STRUCTURE.txt
> > and start your local web server, and you can fix any html+css+javascript
> > issue
> > 
> >> > Experience with releases.json not being in svn in the first place told
> >> > me
> >> > that not having whole json content in svn was just increasing barrier
> >> > to
> >> > commits from whole ASF committers to projects directory visualization
> >> 
> >> Or maybe it was just that the file formats were not clearly documented.
> > 
> > no, the problem was not the format, it was the data (even if format
> > documentation is something we need also).
> 
> But how can one provide the data if the format is not clearly documented?
currently, every json file is generated: nobody has to write such data by hand, 
but run scripts that generate content
This does not mean that documentation is not useful: just that it is a little 
bit less critical
but if we were to hand-write these json files, yes, documentation would be the 
first step

disclaimer: I want to make documentation, I just don't know how to do it with 
json files. I'm interested in a demo on 1 file from people with experience on 
this topic

> 
> >> > 2. doap files in svn (copies of parsed content or generated ones)
> >> > 
> >> > From the beginning of my work on projects-new, I had a question in
> >> > mind:
> >> > is
> >> > DOAP itself a problem (since not easy, not well understood), or are
> >> > there
> >> > just problems about the way DOAP is used and explained to ASF
> >> > committers
> >> > (= not DOAP experts, if DOAP experts exist)?
> >> > 
> >> > Any discussion on this list about that question lead to some people
> >> > wanting to simply drop DOAP, because for them, implicitely, the format
> >> > itself/only was the problem, without answering previous question (and
> >> > without providing a better alternative = the show stopper for me: no,
> >> > simply telling "json" is not a sufficient answer, there has at least to
> >> > be a schema)
> >> 
> >> Indeed.
> >> Abandoning DOAP and using JSON will just lead to exactly the same
> >> problem down the line: *unless* the JSON schema is well designed and
> >> documented. Likewise for any other replacement.
> > 
> > +1
> > 
> >> It's usually obvious to the code/data developers who create the
> >> initial codebase how everything hangs together, but as the codebase
> >> matures the detailed knowledge will be lost unless it is documented.
> >> It's usually possible to tweak existing code to make small fixes
> >> without fully understanding the whole, but without a clear
> >> understanding of the way the parts are designed to work together the
> >> code (and data) tends to grow like spaghetti.
> >> 
> >> The way that the ASF used the DOAP files was not properly documented
> >> originally (it's a bit better now), but that tends to be the way with
> >> developers - documentation is done after the event, if at all. This is
> >> true of many of the new JSON files.
> > 
> > IMHO, here, the requirement on documentation is even higher since a lot of
> > people will need to write data, without being involved in the code using
> > the data.
> > 
> >> Note that when we refer to DOAP in this

Re: Unnecessary SVN commits [was: svn commit: r1691273 - in /comdev/projects.apache.org/site: doap/cxf/cxf.rdf doap/httpd/httpd.rdf json/foundation/projects.json json/projects/cxf.json json/projects/h

[Hervé BOUTEMY]

Le lundi 20 juillet 2015 01:43:11 sebb a écrit :
> On 19 July 2015 at 14:18, Hervé BOUTEMY  wrote:
> > time to explain what I have in mind, because I understand the reactions
> > about these svn content questions: but I need to explain why I think that
> > it's not a bug, it's a feature :)
> > 
> > 
> > 1. generated json files in svn
> > 
> > even if they are generated, these ones are IMHO useful to ease people just
> > wanting to work on information rendering, ie the site's html+javascript
> 
> The current files can still be accessed from the web server; they
> don't have to be in SVN to be useful.
seems I was not clear: the question is not the web server.
The question is the lambda ASF committer who does not have access to the web 
server but would like to contribute to the web part, fix an issue he sees on 
the live site: currently, one svn checkout, read STRUCTURE.txt and start your 
local web server, and you can fix any html+css+javascript issue

> 
> > Experience with releases.json not being in svn in the first place told me
> > that not having whole json content in svn was just increasing barrier to
> > commits from whole ASF committers to projects directory visualization
> 
> Or maybe it was just that the file formats were not clearly documented.
no, the problem was not the format, it was the data (even if format 
documentation is something we need also).

> 
> > 2. doap files in svn (copies of parsed content or generated ones)
> > 
> > From the beginning of my work on projects-new, I had a question in mind:
> > is
> > DOAP itself a problem (since not easy, not well understood), or are there
> > just problems about the way DOAP is used and explained to ASF committers
> > (= not DOAP experts, if DOAP experts exist)?
> > 
> > Any discussion on this list about that question lead to some people
> > wanting to simply drop DOAP, because for them, implicitely, the format
> > itself/only was the problem, without answering previous question (and
> > without providing a better alternative = the show stopper for me: no,
> > simply telling "json" is not a sufficient answer, there has at least to
> > be a schema)
> 
> Indeed.
> Abandoning DOAP and using JSON will just lead to exactly the same
> problem down the line: *unless* the JSON schema is well designed and
> documented. Likewise for any other replacement.
+1

> 
> It's usually obvious to the code/data developers who create the
> initial codebase how everything hangs together, but as the codebase
> matures the detailed knowledge will be lost unless it is documented.
> It's usually possible to tweak existing code to make small fixes
> without fully understanding the whole, but without a clear
> understanding of the way the parts are designed to work together the
> code (and data) tends to grow like spaghetti.
> 
> The way that the ASF used the DOAP files was not properly documented
> originally (it's a bit better now), but that tends to be the way with
> developers - documentation is done after the event, if at all. This is
> true of many of the new JSON files.
IMHO, here, the requirement on documentation is even higher since a lot of 
people will need to write data, without being involved in the code using the 
data.

> 
> Note that when we refer to DOAP in this context we are referring to
> the XML representation.
> There might be a different representation that is easier to use.
I'm not a semantic web expert: could we try to write down (in the wiki for 
example) one project RDF/XML DOAP and its equivalent in another notation?

> 
> After all, we are trying to describe projects, so Description Of A
> Project should be a good fit, even if using XML to define the DOAP is
> not so suitable.
+1 on the general logic
but I could not find a good documentation on DOAP apart from the DOAP schema 
itself: did I miss something?

> 
> Do we really want to design a new DOAP schema using JSON?
I rephrase the same question: will we do better docuemntation if we reinvent 
the wheel? (the answer may be "yes", but need real investment)

> 
> > Then my first steps were:
> > - improve projects new site and switch from projects old, as each project
> > page on projects-new more clearly shows information that comes from the
> > project's DOAP file (IMHO, projects old was failing at this, no pun
> > intended): we'll see if ASF committers can improve their DOAP files (as
> > some already did since the switch)
> 
> Yes, better presentation of the data should help to persuade PMCs to
> fix/improve their data.
> 
> > - the new DOAP listings location, that is like projects old, but
> > si

Re: Unnecessary SVN commits [was: svn commit: r1691273 - in /comdev/projects.apache.org/site: doap/cxf/cxf.rdf doap/httpd/httpd.rdf json/foundation/projects.json json/projects/cxf.json json/projects/h

[Hervé BOUTEMY]

time to explain what I have in mind, because I understand the reactions about 
these svn content questions: but I need to explain why I think that it's not a 
bug, it's a feature :)


1. generated json files in svn

even if they are generated, these ones are IMHO useful to ease people just 
wanting to work on information rendering, ie the site's html+javascript
Experience with releases.json not being in svn in the first place told me that 
not having whole json content in svn was just increasing barrier to commits 
from whole ASF committers to projects directory visualization


2. doap files in svn (copies of parsed content or generated ones)

>From the beginning of my work on projects-new, I had a question in mind: is 
DOAP itself a problem (since not easy, not well understood), or are there just 
problems about the way DOAP is used and explained to ASF committers (= not 
DOAP experts, if DOAP experts exist)?

Any discussion on this list about that question lead to some people wanting to 
simply drop DOAP, because for them, implicitely, the format itself/only was 
the problem, without answering previous question (and without providing a 
better alternative = the show stopper for me: no, simply telling "json" is not 
a sufficient answer, there has at least to be a schema)

Then my first steps were:
- improve projects new site and switch from projects old, as each project page 
on projects-new more clearly shows information that comes from the project's 
DOAP file (IMHO, projects old was failing at this, no pun intended): we'll see 
if ASF committers can improve their DOAP files (as some already did since the 
switch)
- the new DOAP listings location, that is like projects old, but simplified 
since only focused on DOAP listings and content (no code): 
http://svn.apache.org/viewvc/comdev/projects.apache.org/data/

These are only the first steps IMHO before deciding if we should continue with 
DOAP or find a better alternative (yet to be found/proposed).

I see 2 other steps:
- clarify what committee DOAP files (also called "PMC descriptors") are 
supposed to contain, and how projects (maintained by the committees) are 
supposed to link to the committee. As discussed previously, current convention 
[1] is really strange. And PMC members list are easier updated automatically 
from committee-info.txt than manually.

- prefer https://projects.apache.org/doap/ to 
https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/
IMHO, /doap/ in projects site, with every ASF committer commit access, and its 
per-committee directory containing both PMC descriptor and projects DOAP 
descriptors would be easier to understand and maintain than an XML listing in 
svn then descriptors in a lot of different places
And this would give a good canonical url for each DOAP file (easing work on 
previous item)


I know this is a long post: sorry, could not make it shorter.

Switching from projects old to projects new without changing much things to 
DOAP sources was only the beginning of a story: we need to define next steps.

Regards,

Hervé


[1] https://projects-old.apache.org/guidelines.html see 2 last bullets:
- PMCs can be referenced as an rdf:resource that points at 
http://.apache.org/. e.g. 
http://httpd.apache.org/"; />. 
In this case, the PMC descriptor file must be called .rdf and must be 
stored in the directory: 
http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/
- PMCs descriptors can also be stored anywhere else (e.g. on the TLP website 
or in SVN), in which case they must be referenced using the full URL, for 
example 
http://tlp.apache.org/pmc/tlp.rdf"; />

Le dimanche 19 juillet 2015 09:48:17 sebb a écrit :
> On 15 July 2015 at 22:11,   wrote:
> > Author: hboutemy
> > Date: Wed Jul 15 21:11:32 2015
> > New Revision: 1691273
> > 
> > URL: http://svn.apache.org/r1691273
> > Log:
> > import projects DOAP files updates
> > 
> > Modified:
> > comdev/projects.apache.org/site/doap/cxf/cxf.rdf
> > comdev/projects.apache.org/site/doap/httpd/httpd.rdf
> > comdev/projects.apache.org/site/json/foundation/projects.json
> > comdev/projects.apache.org/site/json/projects/cxf.json
> > comdev/projects.apache.org/site/json/projects/httpd.json
> 
> Why are these copies being committed to SVN?
> 
> Projects-old makes do with a local copy of the files which it keeps in
> sync with the ones listed in files.xml
> 
> It seems wasteful and unnecessary to create new backup copies in SVN.
> 
> AFAICT they are bound to be out of date as they are committed manually.
> 
> Furthermore there is also a  danger that the wrong copy may be updated
> by someone.

Re: Fw: Is https://projects-new.apache.org/ ready for prime time?

[Hervé BOUTEMY]

no need for COMDEV Jira issue: it's Hadoop DOAP that requires to be improved, 
that is under Hadoop project responsibility in Hadoop svn:
http://hadoop.apache.org/doap.rdf

Regards,

Hervé

Le mercredi 15 juillet 2015 13:24:55 Ajoy Bhatia a écrit :
> Just read this page: https://projects.apache.org/about.html
> 
> I'll create a COMDEV ticket and try to fix it myself. This would be my
> first contribution to the Apache community.  :-)
> 
> - Ajoy
> 
> On Wed, Jul 15, 2015 at 1:19 PM, Ajoy Bhatia  wrote:
> > Hi all,
> > 
> > On https://projects.apache.org/projects.html?category, the only 2
> > occurrences of "hadoop" are the link to the Apache Hadoop
> >  project page in the
> > *database* 
> > category, and as the *hadoop*
> >  category
> > itself.
> > 
> > I think that Apache Hadoop should also be listed in the *big-data*
> >  category,
> > as well as in the eponymous *hadoop*
> >  category.
> > Don't you agree?
> > 
> > Thanks...
> > - Ajoy
> > 
> > 
> > 
> > On Tue, Jul 14, 2015 at 4:33 PM, Daniel Gruno 
> > 
> > wrote:
> >> Fixed in r1691109, thanks for spotting this.
> >> 
> >> With regards,
> >> Daniel.
> >> 
> >> On 2015-07-15 01:21, Ted Dunning wrote:
> >>> The label on the second pie graph is broken.  It refers to language (cut
> >>> and paste from the first caption, I think).
> >>> 
> >>> On Tue, Jul 14, 2015 at 10:40 AM, Sally Khudairi  wrote:
> >>>  So ...we've had a tweet from Roman last month, and now JimJag (bcc'd)
> >>>  
>  has
>  done so as well
>  
>  https://twitter.com/jimjag/status/620940463558782976
>  
>  
>  Are we officially live yet?
>  
>  If not, please let me know when I can promote.
>  
>  Cheers,
>  Sally
>  
>  
>  From: Sally Khudairi 
>  To: jan i ; "dev@community.apache.org" <
>  dev@community.apache.org>
>  Cc: David Crossley ; Sally Khudairi   
>  Sent: Saturday, 20 June 2015, 6:53
>  Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime
>  time?
>  
>  
>  
>  Aha!
>  
>  OK --that's exactly it. I didn't realize that it was going to replace
>  the
>  old link.
>  
>  So yes, you are correct, Jan, we don't want to do that.
>  
>  As such, I'll be standing by to hear when you (collectively) are ready.
>  
>  Thanks again,
>  
>    Sally
>  
>  [From the mobile; please excuse top-posting, spelling/spacing errors,
>  and
>  brevity]
>  
>  
>  
>  - Reply message -
>  From: "jan i" 
>  To: "dev@community.apache.org" 
>  Cc: "David Crossley" , "Sally Khudairi" <
>  s...@apache.org>
>  Subject: Fw: Is https://projects-new.apache.org/ ready for prime time?
>  Date: Sat, Jun 20, 2015 06:39
>  
>  
>  
>  
>  
>  On 20 June 2015 at 12:34, Sally Khudairi   .invalid>
>  wrote:
>  
>  Thanks, David!
>  
> > I noticed that Roman tweeted the link yesterday, so I guess the cat is
>  
>  out of the bag, as the saying goes.
>  
> > As such, barring any objections, I'll start spreading the word.
> > 
> >  Do we really want to do marketing on the temporary URL ?
>  
>  In my opinion, we should do some renaming so the current one is called
>  -old and the new one replaces the current one.
>  
>  
>  rgds
>  
>  jan i.
>  
>   Are there plans in place to link this from the apache.org homepage?
>   
> > Thanks again,
> > Sally
> > 
> > 
> > [From the mobile; please excuse top-posting, spelling/spacing errors,
> > and
>  
>  brevity]
>  
> > - Reply message -
> > 
> > From: "David Crossley" 
> > To: , "Sally Khudairi" 
> > Subject: Fw: Is https://projects-new.apache.org/ ready for prime time?
> > Date: Sat, Jun 20, 2015 03:03
> > 
> > Previous discussion here was about how to maintain the
> > actual project data.
> > Also various items listed here:
> > https://projects-new.apache.org/about.html
> > 
> > ~David
> > 
> > On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote:
> >> Hello Uli and the Apache ComDev team --I hope this message finds you
> > 
> > well.
> > 
> > Per below, I'm interested in promoting the new Projects page.
> > 
> >> Can you please let me know if/when we're ready to do so?
> >> Thanks so much,
> >> Sally
> >> 
> >>  - Forwarded Message -
> >>
> >>From: David Nalley 
> >>   
> >>   To: Sally Khudairi 
> >> 
> >> Cc: D

Re: svn commit: r1691050 - /comdev/projects.apache.org/site/.htaccess

[Hervé BOUTEMY]

the .htaccess is not taken into account
does anybody know how to have projects.a.o use this .htaccess?

Regards,

Hervé

Le mardi 14 juillet 2015 18:35:48 hbout...@apache.org a écrit :
> Author: hboutemy
> Date: Tue Jul 14 18:35:48 2015
> New Revision: 1691050
> 
> URL: http://svn.apache.org/r1691050
> Log:
> added htaccess to avoid some 404 from links to projects old
> 
> Added:
> comdev/projects.apache.org/site/.htaccess   (with props)
> 
> Added: comdev/projects.apache.org/site/.htaccess
> URL:
> http://svn.apache.org/viewvc/comdev/projects.apache.org/site/.htaccess?rev=
> 1691050&view=auto
> ===
> === --- comdev/projects.apache.org/site/.htaccess (added)
> +++ comdev/projects.apache.org/site/.htaccess Tue Jul 14 18:35:48 2015
> @@ -0,0 +1,10 @@
> +# feature only available in projects-old
> +RedirectMatch ^/feeds/(.*)$ https://projects-old.apache.org/feeds/$1
> +
> +# feature that changed url in projects-new
> +RedirectMatch Permanent ^/projects/(.*).html$
> https://projects.apache.org/project.html?$1 +Redirect Permanent
> /indexes/alpha.html https://projects.apache.org/projects.html +Redirect
> Permanent /indexes/category.html
> https://projects.apache.org/projects.html?category +Redirect Permanent
> /indexes/language.html https://projects.apache.org/projects.html?language
> +Redirect Permanent /indexes/pmc.html
> https://projects.apache.org/projects.html?pmc +Redirect Permanent
> /indexes/quick.html https://projects.apache.org/projects.html
> 
> Propchange: comdev/projects.apache.org/site/.htaccess
> 
> -- svn:eol-style = native
> 
> Propchange: comdev/projects.apache.org/site/.htaccess
> 
> -- svn:keywords = Author Date Id Revision

Re: Fw: Is https://projects-new.apache.org/ ready for prime time?

[Hervé BOUTEMY]

yes, we are officially live since sunday night
https://projects.apache.org/

Regards,

Hervé

Le mardi 14 juillet 2015 17:40:02 Sally Khudairi a écrit :
> So ...we've had a tweet from Roman last month, and now JimJag (bcc'd) has
> done so as well
> 
> https://twitter.com/jimjag/status/620940463558782976
> 
> 
> Are we officially live yet?
> 
> If not, please let me know when I can promote.
> 
> Cheers,
> Sally
> 
> 
> From: Sally Khudairi 
> To: jan i ; "dev@community.apache.org"
>  Cc: David Crossley ; Sally
> Khudairi  Sent: Saturday, 20 June 2015, 6:53
> Subject: Re: Fw: Is https://projects-new.apache.org/ ready for prime time?
> 
> 
> 
> Aha!
> 
> OK --that's exactly it. I didn't realize that it was going to replace the
> old link.
> 
> So yes, you are correct, Jan, we don't want to do that.
> 
> As such, I'll be standing by to hear when you (collectively) are ready.
> 
> Thanks again,
>  Sally
> 
> 
> [From the mobile; please excuse top-posting, spelling/spacing errors, and
> brevity]
> 
> 
> 
> - Reply message -
> From: "jan i" 
> To: "dev@community.apache.org" 
> Cc: "David Crossley" , "Sally Khudairi" 
> Subject: Fw: Is https://projects-new.apache.org/ ready for prime time?
> Date: Sat, Jun 20, 2015 06:39
> 
> 
> 
> 
> 
> On 20 June 2015 at 12:34, Sally Khudairi 
> wrote:
> 
> Thanks, David!
> 
> >I noticed that Roman tweeted the link yesterday, so I guess the cat is out
> >of the bag, as the saying goes.
> >
> >As such, barring any objections, I'll start spreading the word.
> 
> Do we really want to do marketing on the temporary URL ?
> 
> 
> In my opinion, we should do some renaming so the current one is called -old
> and the new one replaces the current one.
> 
> 
> rgds
> 
> jan i.
> 
> >Are there plans in place to link this from the apache.org homepage?
> >
> >Thanks again,
> >Sally
> >
> >
> >[From the mobile; please excuse top-posting, spelling/spacing errors, and
> >brevity]
> >
> >- Reply message -
> >
> >From: "David Crossley" 
> >To: , "Sally Khudairi" 
> >Subject: Fw: Is https://projects-new.apache.org/ ready for prime time?
> >Date: Sat, Jun 20, 2015 03:03
> >
> >Previous discussion here was about how to maintain the
> >actual project data.
> >Also various items listed here:
> >https://projects-new.apache.org/about.html
> >
> >~David
> >
> >On Fri, Jun 19, 2015 at 08:55:52PM +, Sally Khudairi wrote:
> >> Hello Uli and the Apache ComDev team --I hope this message finds you
> >> well.
> >> Per below, I'm interested in promoting the new Projects page.
> >> Can you please let me know if/when we're ready to do so?
> >> Thanks so much,
> >> Sally
> >> 
> >> - Forwarded Message -
> >>   
> >>   From: David Nalley 
> >>  
> >>  To: Sally Khudairi 
> >> 
> >> Cc: Daniel Gruno ; ASF Infrastructure
> >> >> 
> >>  Sent: Friday, June 19, 2015 11:50 AM
> >>  Subject: Re: Is https://projects-new.apache.org/ ready for prime time?
> >> 
> >> Hi Sally:
> >> 
> >> projects-new.apache.org is a ComDev managed resource, not an
> >> infrastructure managed resource. I think the PMC has had a discussion
> >> or two about when to migrate projects-new to projects.a.o
> >> 
> >> --David
> >> 
> >> 
> >> 
> >> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi
> >> 
> >>  wrote:
> >> > Hello Daniel and David --I hope you are both well.
> >> > 
> >> > 
> >> > I was wondering if the new Projects page at
> >> > 
> >> > https://projects-new.apache.org/
> >> > 
> >> > was ready to be publicly deployed/announced/promoted.
> >> > 
> >> > There's so much great information there and it's an incredible resource
> >> > (I use it every week for the News Round-ups and we relied on it for
> >> > the Annual Report), if there's no reason why it should still be in
> >> > stealth mode, I'd like to shout out about it from the rooftops.
> >> > 
> >> > Just let me know if we're good to go and if there are any
> >> > disclaimers/caveats we should be aware of.
> >> > 
> >> > Warm thanks,
> >> > Sally
> >> > 
> >> > 
> >> > = = = = =
> >> > vox +1 617 921 8656
> >> > off2 +1 646 583 3362
> >> > skype sallykhudairi

the new http://projects.apache.org/ is live

[Hervé BOUTEMY]

Hi,

As the title says, projects is now projects-new:
http://projects.apache.org

The old projects is available at
https://projects-old.apache.org/

(there is currently a bug in config for http://projects-old.apache.org/ that 
should be worked on tomorrow, tracked in 
https://issues.apache.org/jira/browse/INFRA-9453 )


Please report if there is any issue

Regards,

Hervé

Re: [Projects New] Why are output files stored in SVN?

[Hervé BOUTEMY]

true, everything can be regenerated

but there are IMHO multiple ideas behind storing the full site in svn:
- not serve http from projects-vm but from classical resilient httpd (just let 
projects-vm just run the cron jobs)
- have a centralized history of whole data (be it source rdf in a central 
place or derived json files)

Regards,

Hervé

Le dimanche 12 juillet 2015 16:58:29 sebb a écrit :
> Why does projects new need to store changes to the files it generates in
> SVN?
> 
> AFAICT, all (or nearly all) the files are generated from data that is
> already in SVN.
> 
> There are perhaps a few files that contain historic data that is not
> otherwise available.
> These could be stored as template files in SVN in case the working
> files need to be regenerated.
> But otherwise, I don't see the point in storing changes to derived data in
> SVN.
> 
> We should be striving to reduce data duplication, not increase it...

Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt

[Hervé BOUTEMY]

Le dimanche 12 juillet 2015 15:41:13 sebb a écrit :
> On 12 July 2015 at 14:56, Hervé BOUTEMY  wrote:
> > Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
> >> On 12 July 2015 at 13:58,   wrote:
> >> > Author: hboutemy
> >> > Date: Sun Jul 12 12:58:09 2015
> >> > New Revision: 1690454
> >> > 
> >> > URL: http://svn.apache.org/r1690454
> >> > Log:
> >> > updated explanation on import scripts vs update scripts
> >> > 
> >> > Modified:
> >> > comdev/projects.apache.org/scripts/README.txt
> >> > 
> >> > Modified: comdev/projects.apache.org/scripts/README.txt
> >> > URL:
> >> > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README.
> >> > tx
> >> > t?rev=1690454&r1=1690453&r2=1690454&view=diff
> >> > ===
> >> > ==
> >> > = --- comdev/projects.apache.org/scripts/README.txt (original)
> >> > +++ comdev/projects.apache.org/scripts/README.txt Sun Jul 12 12:58:09
> >> > 2015
> >> > 
> >> > @@ -43,3 +43,8 @@ various sources:
> >> >in: data/projects.xml + projects' DOAP files
> >> >out: site/json/projects/*.json + site/json/foundation/projects.json
> >> >
> >> >+ site/doap/{committeeId}/{project}.rdf
> >> > 
> >> > +
> >> > +NOTICE: what prevents import scripts to be added to cron?
> >> > +1. parse committees.py requires committee-info.txt, which is not
> >> > available on project-vm (require authentication)
> >> 
> >> Agreed this means the script must be run by a process with suitable karma
> >> 
> >> > +2. both scripts not only update files but sometimes need to add new
> >> > files
> >> > (new committees or new projects) or move +   (projects going to Attic
> >> > or
> >> > retired committees)
> >> 
> >> Why should it make a difference if files need to be added?
> >> There is already a cronjob that detects new files and runs 'svn add' for
> >> them
> > 
> > the real problem is when moving a file is required: if we blindly add new
> > files for files that should be moved, not only do we get too much files,
> > but when removing the old file we loose history (that could have been
> > useful)
> In which case, why not run 'svn add' and 'svn mv' as part of the
> script where necessary?
we need to detect when a project moves to Attic
then integrate svn commands to the python script

feasible, but adds complexity...

> 
> This would be safer than the cronjob which assumes that all new files
> are to be added to SVN.

Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt

[Hervé BOUTEMY]

Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
> On 12 July 2015 at 13:58,   wrote:
> > Author: hboutemy
> > Date: Sun Jul 12 12:58:09 2015
> > New Revision: 1690454
> > 
> > URL: http://svn.apache.org/r1690454
> > Log:
> > updated explanation on import scripts vs update scripts
> > 
> > Modified:
> > comdev/projects.apache.org/scripts/README.txt
> > 
> > Modified: comdev/projects.apache.org/scripts/README.txt
> > URL:
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README.tx
> > t?rev=1690454&r1=1690453&r2=1690454&view=diff
> > =
> > = --- comdev/projects.apache.org/scripts/README.txt (original)
> > +++ comdev/projects.apache.org/scripts/README.txt Sun Jul 12 12:58:09 2015
> > 
> > @@ -43,3 +43,8 @@ various sources:
> >in: data/projects.xml + projects' DOAP files
> >out: site/json/projects/*.json + site/json/foundation/projects.json
> >
> >+ site/doap/{committeeId}/{project}.rdf
> > 
> > +
> > +NOTICE: what prevents import scripts to be added to cron?
> > +1. parse committees.py requires committee-info.txt, which is not
> > available on project-vm (require authentication)
> Agreed this means the script must be run by a process with suitable karma
> 
> > +2. both scripts not only update files but sometimes need to add new files
> > (new committees or new projects) or move +   (projects going to Attic or
> > retired committees)
> 
> Why should it make a difference if files need to be added?
> There is already a cronjob that detects new files and runs 'svn add' for
> them
the real problem is when moving a file is required: if we blindly add new files 
for files that should be moved, not only do we get too much files, but when 
removing the old file we loose history (that could have been useful)

Regards,

Hervé

Re: svn commit: r1689145 - in /comdev/projects.apache.org/site: doap/whimsy/whimsy.rdf json/projects/whimsy.json

[Hervé BOUTEMY]

ok
parsecommittees.py updated (with generated content) in 
http://svn.apache.org/r1689183

notice http://whimsical.apache.org/ does not really gives meaningful result at 
the moment

Regards,

Hervé

Le samedi 4 juillet 2015 15:48:20 sebb a écrit :
> On 4 July 2015 at 12:36,   wrote:
> > Author: hboutemy
> > Date: Sat Jul  4 11:36:45 2015
> > New Revision: 1689145
> > 
> > URL: http://svn.apache.org/r1689145
> > Log:
> > added Whimsy files
> > 
> > Added:
> > comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf
> > comdev/projects.apache.org/site/json/projects/whimsy.json
> > 
> > Added: comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf
> > URL:
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/site/doap/whimsy/
> > whimsy.rdf?rev=1689145&view=auto
> > =
> > = --- comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf (added)
> > +++ comdev/projects.apache.org/site/doap/whimsy/whimsy.rdf Sat Jul  4
> > 11:36:45 2015 @@ -0,0 +1,40 @@
> > +
> > +
> > + > + xmlns="http://usefulinc.com/ns/doap#";
> > + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
> > + xmlns:asfext="http://projects.apache.org/ns/asfext#";
> > + xmlns:foaf="http://xmlns.com/foaf/0.1/";>
> > +
> > +  http://whimsy.apache.org";>
> > +2015-06-25
> > +http://spdx.org/licenses/Apache-2.0"; />
> > +Apache Whimsy
> > +http://whimsy.apache.org/"; />
> 
> That's the URL of the Whimsy service, not the PMC/TLP.
> The TLP website will be at http://whimsical.apache.org/
> 
> > +http://whimsy.apache.org"; />
> > +Whimsy is a site where a set of absolutely unnecessary yet
> > often quite handy applications are deployed.  +   
> > JavaScript
> > +http://projects.apache.org/category/content";
> > /> +
> > +  
> > + > rdf:resource="https://svn.apache.org/repos/infra/infrastructure/trunk/pro
> > jects/whimsy"/> + > rdf:resource="http://svn.apache.org/repos/infra/infrastructure/trunk/proj
> > ects/whimsy"/> +  
> > +
> > +  
> > +
> > 
> > Added: comdev/projects.apache.org/site/json/projects/whimsy.json
> > URL:
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/site/json/project
> > s/whimsy.json?rev=1689145&view=auto
> > =
> > = --- comdev/projects.apache.org/site/json/projects/whimsy.json
> > (added) +++ comdev/projects.apache.org/site/json/projects/whimsy.json Sat
> > Jul  4 11:36:45 2015 @@ -0,0 +1,14 @@
> > +{
> > +"category": "content",
> > +"created": "2015-06-25",
> > +"doap":
> > "https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/
> > doap_Whimsy.rdf", +"homepage": "http://whimsy.apache.org/";,
> 
> If this is the homepage for the Whimsy product, then that is correct,
> otherwise see above.
> 
> > +"license": "http://spdx.org/licenses/Apache-2.0";,
> > +"name": "Apache Whimsy",
> > +"pmc": "whimsy",
> > +"programming-language": "JavaScript",
> > +"repository": [
> > +"https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy";
> > +],
> > +"shortdesc": "Whimsy is a site where a set of absolutely unnecessary yet
> > often quite handy applications are deployed. " +}
> > \ No newline at end of file

Re: switching projects to projects-old and project-new to projects

[Hervé BOUTEMY]

issue created https://issues.apache.org/jira/browse/INFRA-9916

I'll see on HipChat who will work on this with me

Regards,

Hervé

Le samedi 27 juin 2015 12:20:18 jan i a écrit :
> On 27 June 2015 at 12:04, Hervé BOUTEMY  wrote:
> > After recent discussions, I updated projects-new to be completely
> > decoupled
> > from projects-old: see https://projects-new.apache.org/about.html
> > 
> > Now, the switch can happen smoothly whenever we want.
> > 
> > 
> > Now, we just have:
> > 
> > 1. to decide when we do it (and communicate about it)
> 
> Choose a day with infra (jump on hipchat that is the fastest), where you
> and infra have time.
> (I can be around for testing nearly anytime, given a notice).
> 
> I would mail it on this list.
> I would furthermore send an email to all PMCS (I can help with sending the
> mail, if needed), describing what
> changes are affecting them.
> 
> > 2. determine who (probably in infra) can do the switch (and deploy
> > projects-
> > new in classical svnpubsub Apache sites mechanism), without breaking
> > projects-
> > old cron jobs
> 
> yes it is infra, and you should make a jira + talk with them. There are
> several people
> in infra who can do this blindfolded (clever guys), but they are busy so it
> is easiest
> to coordinate with them.
> 
> > At this point, I don't see what I can do more on my own.
> 
> a bit there is, see above.
> 
> rgds
> jan i.
> 
> > Regards,
> > 
> > Hervé

Re: Reporter.apache.org displaying incorrect data - who is responsible for the host?

[Hervé BOUTEMY]

Le mercredi 1 juillet 2015 09:10:42 sebb a écrit :
> On 1 July 2015 at 07:02, Hervé BOUTEMY  wrote:
> > I asked about it one week ago (with analysis of the VM state), but got no
> > answer.
> > Seems the only one to know is Daniel, and he doesn't check this ML or
> > doesn't have time.
> > 
> > I have access to the VM: it was given for projects-new.
> > Technically, I can change reporter too, but since we're starting from an
> > unexpected status (no svn checkout, files on the VM that are not part of
> > svn),
> If you can create a copy of the files on the VM I could ensure any
> local changes are reflected in SVN.
dump available in people.apache.org:/home/hboutemy/reporter.apache.org.tgz

> It would help also to have details of the crontab entries.
# m h  dom mon dow   command
00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4 
podlings.py
00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4 
parsecommitters.py
00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4 
parsechairs.py
00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4 
countaccounts.py
00 00 * * * cd /var/www/projects.apache.org/scripts/cronjobs && python3.4 
parsereleases.py
00 4,12,20 * * * cd /var/www/reporter.apache.org/data && python3.4 
parsepmcs.py
00 01 * * * cd /var/www/reporter.apache.org/ && python mailglomper.py
00 09 * * * cd /var/www/reporter.apache.org/ && python readjira.py
00 12 * * * curl "(removed)" > 
/var/www/reporter.apache.org/data/mailinglists.json



once content is checked against waht is in svn, we could probably copy and run 
pubsubber.py from projects.a.o so svn updates are propagated to the vm

Regards,

Hervé

> 
> > I didn't want to change the VM content without asking before.
> > 
> > 
> > At the moment, I want to finish projects new switch: then I'll probably
> > have more time to help on reporter.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le mardi 30 juin 2015 01:20:46 sebb a écrit :
> >> Reporter.apache.org is showing misleading PMC membership data.
> >> 
> >> As this is used in board reports, it really ought to be fixed ASAP.
> >> 
> >> However the fixes I made to SVN have not been applied, and there is no
> >> documentation I could find on how the host has been set up - nor how
> >> the faulty data is generated.
> >> 
> >> Who is responsible for maintaining the host and updating the software on
> >> it?

Re: Reporter.apache.org displaying incorrect data - who is responsible for the host?

[Hervé BOUTEMY]

I asked about it one week ago (with analysis of the VM state), but got no 
answer.
Seems the only one to know is Daniel, and he doesn't check this ML or doesn't 
have time.

I have access to the VM: it was given for projects-new.
Technically, I can change reporter too, but since we're starting from an 
unexpected status (no svn checkout, files on the VM that are not part of svn), 
I didn't want to change the VM content without asking before.


At the moment, I want to finish projects new switch: then I'll probably have 
more time to help on reporter.

Regards,

Hervé

Le mardi 30 juin 2015 01:20:46 sebb a écrit :
> Reporter.apache.org is showing misleading PMC membership data.
> 
> As this is used in board reports, it really ought to be fixed ASAP.
> 
> However the fixes I made to SVN have not been applied, and there is no
> documentation I could find on how the host has been set up - nor how
> the faulty data is generated.
> 
> Who is responsible for maintaining the host and updating the software on it?

switching projects to projects-old and project-new to projects

[Hervé BOUTEMY]

After recent discussions, I updated projects-new to be completely decoupled 
from projects-old: see https://projects-new.apache.org/about.html

Now, the switch can happen smoothly whenever we want.


Now, we just have:

1. to decide when we do it (and communicate about it)

2. determine who (probably in infra) can do the switch (and deploy projects-
new in classical svnpubsub Apache sites mechanism), without breaking projects-
old cron jobs


At this point, I don't see what I can do more on my own.

Regards,

Hervé

Re: svn commit: r1686683 - in /comdev/projects.apache.org/scripts: README.txt import/addpmc.py

[Hervé BOUTEMY]

ok, no answer: I'll re-do the commit this WE

Regards,

Hervé

Le jeudi 25 juin 2015 07:54:44 Hervé BOUTEMY a écrit :
> > do you really think addpmc.py is useful now?
> 
> ping
> 
> Regards,
> 
> Hervé
> 
> Le dimanche 21 juin 2015 16:47:25 Hervé BOUTEMY a écrit :
> > ok, there is a misunderstanding: reverted as first step
> > 
> > then we need to discuss, since I don't see when it may be used given
> > current logic where everything comes from committee-info.txt and rdf
> > files: that's the way I added committees created during last monthes, ie
> > simply running parsecommittees.py
> > 
> > adding committees as json when the committee does not exist in committee-
> > info.txt is a nonsense IMHO: once I added committe-info.txt parsing
> > feature, after long thoughts on it, I really don't see any use for this
> > addpmc.py script
> > 
> > (the discussion about RDF/DOAP is another independant topic, ie where to
> > find information that is not in committee-info.txt)
> > 
> > 
> > do you really think addpmc.py is useful now?
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le dimanche 21 juin 2015 15:52:28 Daniel Gruno a écrit :
> > > Excuse me? That script WAS used for adding new committees to the site,
> > > simple and easy.
> > > Please revert, and don't just delete stuff because you personally don't
> > > use it.
> > > 
> > > WIth regards,
> > > Daniel.
> > > 
> > > On 2015-06-21 03:50, hbout...@apache.org wrote:
> > > > Author: hboutemy
> > > > Date: Sun Jun 21 01:50:14 2015
> > > > New Revision: 1686683
> > > > 
> > > > URL: http://svn.apache.org/r1686683
> > > > Log:
> > > > removed addpmc.py: not used
> > > > 
> > > > Removed:
> > > >  comdev/projects.apache.org/scripts/import/addpmc.py
> > > > 
> > > > Modified:
> > > >  comdev/projects.apache.org/scripts/README.txt
> > > > 
> > > > Modified: comdev/projects.apache.org/scripts/README.txt
> > > > URL:
> > > > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README
> > > > .t
> > > > x
> > > > t?rev=1686683&r1=1686682&r2=1686683&view=diff
> > > > ==
> > > > ==
> > > > =
> > > > = --- comdev/projects.apache.org/scripts/README.txt (original)
> > > > +++ comdev/projects.apache.org/scripts/README.txt Sun Jun 21 01:50:14
> > > > 2015
> > > > 
> > > > @@ -34,8 +34,7 @@ various sources:
> > > > in: foundation/committees.json +
> > > > foundation/committees-retired.json
> > > > +
> > > > committee-info.txt
> > > > (https://svn.apache.org/repos/private/committers/board/committee-i
> > > > nf
> > > > o
> > > > .txt) out: foundation/committees.json +
> > > > foundation/committees-retired.json>
> > > > 
> > > > -- parsepmcs.py: imports PMC data (RDF) from the old
> > > > project.apache.org
> > > > site. No need -  to run that more than once?
> > > > +- parsepmcs.py: imports PMC data (RDF) from the old
> > > > project.apache.org
> > > > site.>
> > > > 
> > > > in:
> > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/p
> > > > ro
> > > > j
> > > > ects/pmc_list.xml + PMC data .rdf files out: foundation/pmcs.json
> > > > 
> > > > @@ -43,8 +42,3 @@ various sources:
> > > > turns them into JSON objects.
> > > > in:
> > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/p
> > > > ro
> > > > j
> > > > ects/files.xml + projects' DOAP files out: projects/*.json +
> > > > foundation/projects.json
> > > > 
> > > > -
> > > > -- addpmc.py
> > > > -  in: foundation/pmcs.json + foundation/committees-evolution.json +
> > > > params
> > > > -  out: foundation/pmcs.json + foundation/committees-evolution.json
> > > > -  list of PMCs with site url (pmcs.json) and monthly list of new
> > > > committees (committees-evolution.json)

Re: Is https://projects-new.apache.org/ ready for prime time?

[Hervé BOUTEMY]

Le vendredi 26 juin 2015 17:46:55 sebb a écrit :
> On 26 June 2015 at 07:12, Hervé BOUTEMY  wrote:
> > that's why I want to switch projects to projects-old and projects-new to
> > projects: be able to work on extracting documentation from projects-old
> > and
> > updating it to match the new location
> 
> That will break the existing links.
> 
> If you want do the switch ahead of fixing the documentation, then one
> way to do it is to ensure that projects-old is set up to point to the
> current projects.a.o.
> 
> Then change projects-new to link to projects-old instead of projects -
> that should be trivial to do.
> 
> Then projects-new can replace projects.a.o.
> 
> Documentation can then be migrated to the new code in the old URL.
yes, of course, these are the exact steps: I just summarised

> 
> > I proposed http://svn.apache.org/viewvc/comdev/projects.apache.org/data/
> > as
> > the new location of DOAP files lists (both PMC and projects) but got no
> > answer
> Did not see that.
> 
> That will break projects-old, so -1 until projects-old has been
> retired unless you can find a way to keep projects-old working with
> the new location.
the idea is to let old data in the old location and not update it any more: 
this won't break anything, just make projects-old less accurate over time
that's not an issue IMHO, since we expect to migrate the doc and shutdown 
projects-old after that, in a few monthes

notice that I think the cron job that updates projects-old should be switched 
off to avoid issues

> 
> AFAIK it's not necessary to move the location.
?
previously, you told having projects-new depending on projects-old was an 
issue and you were right!
and IMHO, it's an issue just because data in projects-old is hard to find for 
someone not expert in the whole system

I'll start to add comments in projects-old data to point to projects-new to 
start the transition

then we'll have to agree on when to really switch (and find who can do it)

Regards,

Hervé

> 
> > if we're ok with that new location, the next step is to stop modifying
> > equivalent files in
> > http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/
> > (or even remove them) but point to the new location
> > 
> > Of course, if ok with the new location, we can immediately add
> > committees.xml and projects.xml pointers to
> > https://projects-new.apache.org/about.html IMHO the simple file names and
> > location in about.html would make things very clear before diggin into
> > more details on DOAP format and conventions (which could be in the Wiki
> > for ease of editing)
> > 
> > 
> > can we agree:
> > 1. on the new data location and content:
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/data/
> 
> No, see above.
> 
> > 2. on the switch then update of everything to match the new location (and
> > stop updating projects-old)
> 
> Not entirely, see above.
> 
> > Regards,
> > 
> > Hervé
> > 
> > Le jeudi 25 juin 2015 09:17:32 vous avez écrit :
> >> On 25 June 2015 at 06:53, Hervé BOUTEMY  wrote:
> >> > Sebb,
> >> > 
> >> > as main maintainer of current http://projects.apache.org/ (AFAIK), are
> >> > you
> >> > ok with switching the url to the new service and renaming current
> >> > service
> >> > to projects-old (to let use time to continue content migration withotu
> >> > loosing anything)? Do you see any show stopper?
> >> 
> >> The main item missing from projects-new is documentation - it
> >> currently points to projects.
> >> It's not immediately obvious how to provide data for the site.
> >> I think the main page needs to provide more of an overview.
> >> 
> >> I think the first step needs to be to improve the projects-new
> >> documentation so it does not rely on the current project pages.
> >> 
> >> Also I notice that it seems p-new relies on parsing
> >> http://people.apache.org/committer-index.html
> >> which in turn parses other data sources.
> >> 
> >> That needs to be fixed.
> >> 
> >> > Of course, I'm interested in your help to maintain the new projects
> >> > site:
> >> > don't hesitate to comment on or change the code.
> >> > 
> >> > Regards,
> >> > 
> >> > Hervé
> >> > 
> >> > Le dimanche 21 juin 2015 17:16:07 jan i a écrit :
> >> >> +1 switch as soon as possible, and then continue working on the data
> >

Re: Is https://projects-new.apache.org/ ready for prime time?

[Hervé BOUTEMY]

that's why I want to switch projects to projects-old and projects-new to 
projects: be able to work on extracting documentation from projects-old and 
updating it to match the new location

I proposed http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ as 
the new location of DOAP files lists (both PMC and projects) but got no answer

if we're ok with that new location, the next step is to stop modifying 
equivalent files in 
http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/ (or even 
remove them) but point to the new location

Of course, if ok with the new location, we can immediately add committees.xml 
and projects.xml pointers to https://projects-new.apache.org/about.html 
IMHO the simple file names and location in about.html would make things very 
clear before diggin into more details on DOAP format and conventions (which 
could be in the Wiki for ease of editing)


can we agree:
1. on the new data location and content: 
http://svn.apache.org/viewvc/comdev/projects.apache.org/data/

2. on the switch then update of everything to match the new location (and stop 
updating projects-old)

Regards,

Hervé

Le jeudi 25 juin 2015 09:17:32 vous avez écrit :
> On 25 June 2015 at 06:53, Hervé BOUTEMY  wrote:
> > Sebb,
> > 
> > as main maintainer of current http://projects.apache.org/ (AFAIK), are you
> > ok with switching the url to the new service and renaming current service
> > to projects-old (to let use time to continue content migration withotu
> > loosing anything)? Do you see any show stopper?
> 
> The main item missing from projects-new is documentation - it
> currently points to projects.
> It's not immediately obvious how to provide data for the site.
> I think the main page needs to provide more of an overview.
> 
> I think the first step needs to be to improve the projects-new
> documentation so it does not rely on the current project pages.
> 
> Also I notice that it seems p-new relies on parsing
> http://people.apache.org/committer-index.html
> which in turn parses other data sources.
> 
> That needs to be fixed.
> 
> > Of course, I'm interested in your help to maintain the new projects site:
> > don't hesitate to comment on or change the code.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le dimanche 21 juin 2015 17:16:07 jan i a écrit :
> >> +1 switch as soon as possible, and then continue working on the data end.
> >> 
> >> rgds
> >> jan i
> >> 
> >> On Sunday, June 21, 2015, Hervé BOUTEMY  wrote:
> >> > Le dimanche 21 juin 2015 15:54:29 jan i a écrit :
> >> > > On 21 June 2015 at 15:48, Daniel Gruno  >> > 
> >> > > wrote:
> >> > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote:
> >> > > >> for me, the new site is ready: there is of course room for
> >> > 
> >> > improvements,
> >> > 
> >> > > >> but
> >> > > >> it is stable and maintainable, waiting for contributions
> >> > > >> 
> >> > > >> notice: I changed the wording to stop using "TLP", but use
> >> > > >> "Committee"
> >> > > >> instead, since TLP cause issues when trying to describe each
> >> > > >> projects
> >> > > >> (the
> >> > > >> software) as TLP or sub-projects
> >> > > >> 
> >> > > >> 
> >> > > >> when doing the switch, we'll need to rename current site as
> >> > > >> projects-
> >> > > >> old.apache.org: there is some content to migrate (DOAP,
> >> > 
> >> > documentation)
> >> > 
> >> > > >> associated to communication with projects on the changes that has
> >> > > >> to
> >> > 
> >> > be
> >> > 
> >> > > >> decoupled from public vizualisation. I'll continue working on it.
> >> > > >> 
> >> > > >> There one choice to do: continue serving the pages from current VM
> >> > > >> or
> >> > > >> serve
> >> > > >> through standard resilient httpds. The VM is useful for cron jobs,
> >> > 
> >> > but is
> >> > 
> >> > > >> not
> >> > > >> absolutely necessary for serving content since I removed online
> >> > 
> >> > content
> >> > 
> >> > > >> editing that caused the VM requirement for conte

Re: Can't reporter.a.o automatically detect version number and release date?

[Hervé BOUTEMY]

I did some work on guessing algorithm for
https://projects-new.apache.org/releases.html
=> the release name is completely calculated from full file name found in /dist

That's the best I could do: not really extract version, but at least extract 
release name
see [1] for more details on code

Notice: sine reporter works at Committee/PMC level, there may be multiple 
projects that are managed by the committee, thus the question is not only to 
extract the version but the project too

Regards,

Hervé

[1] 
http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/cronjobs/parsereleases.py?view=markup

Le jeudi 25 juin 2015 14:31:27 Alex Harui a écrit :
> On 6/25/15, 7:18 AM, "hedh...@gmail.com on behalf of Niclas Hedhman"
>  wrote:
> 
> 
> >If the "format" is published, and the "reward" of following it would be
> >that the reporter picks it up automatically, it could lead to swift
> >adoption ;-)
> 
> 
> You might get push back about having to change naming schemes.
> 
> I’m interested in a list of all current and past releases for my project.
> I was trying to figure out how to mine archive.a.o or the svn log for it.
> I’d be willing to maintain an xml file like in DOAP or elsewhere of not
> just the last, but all releases and links to their downloads with
> “friendly” names for the releases.  Then reporter.a.o could grab from that.
> 
> -Alex
> 
> 
> >
> >On Thu, Jun 25, 2015 at 9:26 PM, Daniel Gruno 
> >wrote:
> >
> >
> >> It has been tried, and it did not work.
> >> People are too inconsistent across projects in how they name their
> >>
> >>release
> >>
> >> files, grabbing the version is nigh impossible.
> >> If we had some form of agreement on how to name files, then it would be
> >> possible.
> >>
> >>
> >>
> >> With regards,
> >> Daniel.
> >>
> >>
> >>
> >>
> >> On 2015-06-25 15:11, Martijn Dashorst wrote:
> >>
> >>
> >>
> >>> Is there a reason why the reporter.a.o can send a message to a release
> >>> manager that it detected a new release, but is incapable of
> >>> determining a version number and release date?
> >>>
> >>>
> >>>
> >>> Martijn
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
> >-- 
> >Niclas Hedhman, Software Developer
> >http://zest.apache.org - New Energy for Java
> 
> 

maintaining reporter.apache.org

[Hervé BOUTEMY]

I noticed reporter.apache.org makes use of some projects-new.apache.org json 
files that have disappeared when adding committee-info.txt parsing

Then I started to dig into reporter.a.o code and update minor parts before 
doing more complex work: I expected that svn updates would be published with 
the VM's svnpubsub daemon, but that didn't happen
And when I looked at reporter.a.o directory on the VM, I discovered that it 
was not a svn checkout

Question: how is reporter.apache.org supposed to be updated? is there a 
release process to deploy source code to the VM?

Regards,

Hervé

Re: svn commit: r1686683 - in /comdev/projects.apache.org/scripts: README.txt import/addpmc.py

[Hervé BOUTEMY]

> do you really think addpmc.py is useful now?
ping

Regards,

Hervé

Le dimanche 21 juin 2015 16:47:25 Hervé BOUTEMY a écrit :
> ok, there is a misunderstanding: reverted as first step
> 
> then we need to discuss, since I don't see when it may be used given current
> logic where everything comes from committee-info.txt and rdf files: that's
> the way I added committees created during last monthes, ie simply running
> parsecommittees.py
> 
> adding committees as json when the committee does not exist in committee-
> info.txt is a nonsense IMHO: once I added committe-info.txt parsing feature,
> after long thoughts on it, I really don't see any use for this addpmc.py
> script
> 
> (the discussion about RDF/DOAP is another independant topic, ie where to
> find information that is not in committee-info.txt)
> 
> 
> do you really think addpmc.py is useful now?
> 
> Regards,
> 
> Hervé
> 
> Le dimanche 21 juin 2015 15:52:28 Daniel Gruno a écrit :
> > Excuse me? That script WAS used for adding new committees to the site,
> > simple and easy.
> > Please revert, and don't just delete stuff because you personally don't
> > use it.
> > 
> > WIth regards,
> > Daniel.
> > 
> > On 2015-06-21 03:50, hbout...@apache.org wrote:
> > > Author: hboutemy
> > > Date: Sun Jun 21 01:50:14 2015
> > > New Revision: 1686683
> > > 
> > > URL: http://svn.apache.org/r1686683
> > > Log:
> > > removed addpmc.py: not used
> > > 
> > > Removed:
> > >  comdev/projects.apache.org/scripts/import/addpmc.py
> > > 
> > > Modified:
> > >  comdev/projects.apache.org/scripts/README.txt
> > > 
> > > Modified: comdev/projects.apache.org/scripts/README.txt
> > > URL:
> > > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README.t
> > > x
> > > t?rev=1686683&r1=1686682&r2=1686683&view=diff
> > > 
> > > =
> > > = --- comdev/projects.apache.org/scripts/README.txt (original)
> > > +++ comdev/projects.apache.org/scripts/README.txt Sun Jun 21 01:50:14
> > > 2015
> > > 
> > > @@ -34,8 +34,7 @@ various sources:
> > > in: foundation/committees.json + foundation/committees-retired.json
> > > +
> > > committee-info.txt
> > > (https://svn.apache.org/repos/private/committers/board/committee-inf
> > > o
> > > .txt) out: foundation/committees.json +
> > > foundation/committees-retired.json>
> > > 
> > > -- parsepmcs.py: imports PMC data (RDF) from the old project.apache.org
> > > site. No need -  to run that more than once?
> > > +- parsepmcs.py: imports PMC data (RDF) from the old project.apache.org
> > > site.>
> > > 
> > > in:
> > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/pro
> > > j
> > > ects/pmc_list.xml + PMC data .rdf files out: foundation/pmcs.json
> > > 
> > > @@ -43,8 +42,3 @@ various sources:
> > > turns them into JSON objects.
> > > in:
> > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/pro
> > > j
> > > ects/files.xml + projects' DOAP files out: projects/*.json +
> > > foundation/projects.json
> > > 
> > > -
> > > -- addpmc.py
> > > -  in: foundation/pmcs.json + foundation/committees-evolution.json +
> > > params
> > > -  out: foundation/pmcs.json + foundation/committees-evolution.json
> > > -  list of PMCs with site url (pmcs.json) and monthly list of new
> > > committees (committees-evolution.json)

Re: Is https://projects-new.apache.org/ ready for prime time?

[Hervé BOUTEMY]

Sebb,

as main maintainer of current http://projects.apache.org/ (AFAIK), are you ok 
with switching the url to the new service and renaming current service to 
projects-old (to let use time to continue content migration withotu loosing 
anything)? Do you see any show stopper?

Of course, I'm interested in your help to maintain the new projects site: 
don't hesitate to comment on or change the code.

Regards,

Hervé

Le dimanche 21 juin 2015 17:16:07 jan i a écrit :
> +1 switch as soon as possible, and then continue working on the data end.
> 
> rgds
> jan i
> 
> On Sunday, June 21, 2015, Hervé BOUTEMY  wrote:
> > Le dimanche 21 juin 2015 15:54:29 jan i a écrit :
> > > On 21 June 2015 at 15:48, Daniel Gruno  > 
> > > wrote:
> > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote:
> > > >> for me, the new site is ready: there is of course room for
> > 
> > improvements,
> > 
> > > >> but
> > > >> it is stable and maintainable, waiting for contributions
> > > >> 
> > > >> notice: I changed the wording to stop using "TLP", but use
> > > >> "Committee"
> > > >> instead, since TLP cause issues when trying to describe each projects
> > > >> (the
> > > >> software) as TLP or sub-projects
> > > >> 
> > > >> 
> > > >> when doing the switch, we'll need to rename current site as projects-
> > > >> old.apache.org: there is some content to migrate (DOAP,
> > 
> > documentation)
> > 
> > > >> associated to communication with projects on the changes that has to
> > 
> > be
> > 
> > > >> decoupled from public vizualisation. I'll continue working on it.
> > > >> 
> > > >> There one choice to do: continue serving the pages from current VM or
> > > >> serve
> > > >> through standard resilient httpds. The VM is useful for cron jobs,
> > 
> > but is
> > 
> > > >> not
> > > >> absolutely necessary for serving content since I removed online
> > 
> > content
> > 
> > > >> editing that caused the VM requirement for content serving AFAIK.
> > 
> > Using
> > 
> > > >> standard httpd will avoid SPOF or eventual load issue.
> > > > 
> > > > What do you mean by 'standard httpd'? It already uses...standard httpd
> > 
> > for
> > 
> > > > serving the site.
> > > > The cron jobs are needed for updating various statistics and data on
> > 
> > the
> > 
> > > > site, they can't just be shut off - they also power
> > 
> > reporter.apache.org.
> > 
> > > Maybe I misunderstood something, I understood that we are using httpd,
> > 
> > but
> > 
> > > in our own vm. In my opinion it would be nicer to use the www.a.o httpd
> > > (sorry
> > > vms have been changing lately so I am not sure where it runs), since
> > > that
> > > would put httpd maintenance on infra instead of comdev.
> > 
> > +1
> > that was what I mean by "standard httpd" (ie not the binary but the
> > machines
> > where it runs)
> > 
> > > > I think the site is ready for a more prominent role, but I find this
> > > > discussion confusing, and I find it somewhat sad that we're gonna
> > > > stick
> > > > with something as arcane as DOAP.
> > > 
> > > +100 !!
> > > 
> > > DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New
> > > (but I know I am only 1 voice).
> > 
> > step by step, please: this will avoid confusion between independant topics
> > 
> > switching without disturbing current conventions/knowledge is something
> > that
> > already takes a long time and energy: I know it because I put a lot of
> > energy
> > on it for a few monthes now!
> > 
> > We started a discussion on this source format topic during april, and
> > AFAIK
> > nobody worked on it.
> > 
> > What I'd like now is to switch: we can discuss later on what we want to
> > change
> > (and communication to every comittees this requires).
> > With the new site, we'll be able to change formats if we want, the only
> > requirement is to have json files for the visualization
> > 
> > 
> > 
> > 
> > Regards,
> > 
> > Hervé
> > 
> > > rgds
> > > j

Re: Format for project data: DOAP/JSON/other (was: Is https://projects-new.apache.org/ ready for prime time?)

[Hervé BOUTEMY]

from my experience when working on the topic, what was very confusing was PMC 
descriptors vs projects DOAP files, and the fact that everything was mixed in 
code [1]

Then I just copied content in projects-new data directory and renamed things 
to be clear about these 2 types of descriptors [2]: IMHO, this will already 
help a lot


Another thing I did is that Python scripts that parse descriptors (projects 
and committees) to generate json files also copy .rdf files in 
/doap/{committeeId} [3]


Last thing at the moment: once again, I'm not a DOAP expert, and there seem to 
be semantic web experts in ASF who should help others better understand how to 
use that. But at the moment, the format seems really not well understood by a 
vast majority of people, even if some advanced rdf files [4] show what can be 
done

Regards,

Hervé

[1] http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/

[2] http://svn.apache.org/viewvc/comdev/projects.apache.org/data/

[3] https://projects-new.apache.org/doap/
http://svn.apache.org/viewvc/comdev/projects.apache.org/site/doap/

[4] http://svn.apache.org/repos/asf/oltu/site/doap_org.apache.oltu.parent.rdf

Le dimanche 21 juin 2015 16:29:19 sebb a écrit :
> [Starting thread with new subject]
> 
> On 21 June 2015 at 16:03, Hervé BOUTEMY  wrote:
> > Le dimanche 21 juin 2015 15:54:29 jan i a écrit :
> >> On 21 June 2015 at 15:48, Daniel Gruno  wrote:
> >> > I think the site is ready for a more prominent role, but I find this
> >> > discussion confusing, and I find it somewhat sad that we're gonna stick
> >> > with something as arcane as DOAP.
> >> 
> >> +100 !!
> >> 
> >> DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New
> >> (but I know I am only 1 voice).
> > 
> > step by step, please: this will avoid confusion between independant topics
> > 
> > switching without disturbing current conventions/knowledge is something
> > that already takes a long time and energy: I know it because I put a lot
> > of energy on it for a few monthes now!
> > 
> > We started a discussion on this source format topic during april, and
> > AFAIK
> > nobody worked on it.
> > 
> > What I'd like now is to switch: we can discuss later on what we want to
> > change (and communication to every comittees this requires).
> > With the new site, we'll be able to change formats if we want, the only
> > requirement is to have json files for the visualization
> 
> Some PMCs are very responsive to requests to maintain DOAP files;
> others take months and multiple reminders even for a simple fix. This
> does not directly affect the format used to hold the data. However it
> does mean that changing to a new format is likely to take a lot of
> time and involve a lot of work. Meanwhile the code will need to
> continue to support the old format.
> 
> It would however be an opportunity to make some improvements. For example:
> - we could be more specific about the data that really needs to be
> maintained by PMCs
> - we could require that the files are stored in a well-known place,
> rather than requiring an index file to find them.

Re: Fw: Is https://projects-new.apache.org/ ready for prime time?

[Hervé BOUTEMY]

Le dimanche 21 juin 2015 15:54:29 jan i a écrit :
> On 21 June 2015 at 15:48, Daniel Gruno  wrote:
> > On 2015-06-21 02:45, Hervé BOUTEMY wrote:
> >> for me, the new site is ready: there is of course room for improvements,
> >> but
> >> it is stable and maintainable, waiting for contributions
> >> 
> >> notice: I changed the wording to stop using "TLP", but use "Committee"
> >> instead, since TLP cause issues when trying to describe each projects
> >> (the
> >> software) as TLP or sub-projects
> >> 
> >> 
> >> when doing the switch, we'll need to rename current site as projects-
> >> old.apache.org: there is some content to migrate (DOAP, documentation)
> >> associated to communication with projects on the changes that has to be
> >> decoupled from public vizualisation. I'll continue working on it.
> >> 
> >> There one choice to do: continue serving the pages from current VM or
> >> serve
> >> through standard resilient httpds. The VM is useful for cron jobs, but is
> >> not
> >> absolutely necessary for serving content since I removed online content
> >> editing that caused the VM requirement for content serving AFAIK. Using
> >> standard httpd will avoid SPOF or eventual load issue.
> > 
> > What do you mean by 'standard httpd'? It already uses...standard httpd for
> > serving the site.
> > The cron jobs are needed for updating various statistics and data on the
> > site, they can't just be shut off - they also power reporter.apache.org.
> 
> Maybe I misunderstood something, I understood that we are using httpd, but
> in our own vm. In my opinion it would be nicer to use the www.a.o httpd
> (sorry
> vms have been changing lately so I am not sure where it runs), since that
> would put httpd maintenance on infra instead of comdev.
+1
that was what I mean by "standard httpd" (ie not the binary but the machines 
where it runs)


> 
> > I think the site is ready for a more prominent role, but I find this
> > discussion confusing, and I find it somewhat sad that we're gonna stick
> > with something as arcane as DOAP.
> 
> +100 !!
> 
> DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New
> (but I know I am only 1 voice).
step by step, please: this will avoid confusion between independant topics

switching without disturbing current conventions/knowledge is something that 
already takes a long time and energy: I know it because I put a lot of energy 
on it for a few monthes now!

We started a discussion on this source format topic during april, and AFAIK 
nobody worked on it.

What I'd like now is to switch: we can discuss later on what we want to change 
(and communication to every comittees this requires).
With the new site, we'll be able to change formats if we want, the only 
requirement is to have json files for the visualization

Regards,

Hervé

> 
> rgds
> jan i.
> 
> > With regards,
> > Daniel.
> > 
> >> but definitely, the site is ready for the switch
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit :
> >>> Hello Uli and the Apache ComDev team --I hope this message finds you
> >>> well.
> >>> Per below, I'm interested in promoting the new Projects page.
> >>> Can you please let me know if/when we're ready to do so?
> >>> Thanks so much,
> >>> Sally
> >>> 
> >>>  - Forwarded Message -
> >>>
> >>>From: David Nalley 
> >>>   
> >>>   To: Sally Khudairi 
> >>> 
> >>> Cc: Daniel Gruno ; ASF Infrastructure
> >>>  Sent: Friday, June 19, 2015 11:50 AM
> >>> 
> >>>   Subject: Re: Is https://projects-new.apache.org/ ready for prime time?
> >>> 
> >>> Hi Sally:
> >>> 
> >>> projects-new.apache.org is a ComDev managed resource, not an
> >>> infrastructure managed resource. I think the PMC has had a discussion
> >>> or two about when to migrate projects-new to projects.a.o
> >>> 
> >>> --David
> >>> 
> >>> 
> >>> 
> >>> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi
> >>> 
> >>>  wrote:
> >>>> Hello Daniel and David --I hope you are both well.
> >>>> 
> >>>> 
> >>>> I was wondering if the new Projects page at
> >>>> 
> >>>> https://projects-new.apache.org/
> >>>> 
> >>>> was ready to be publicly deployed/announced/promoted.
> >>>> 
> >>>> There's so much great information there and it's an incredible resource
> >>>> (I
> >>>> use it every week for the News Round-ups and we relied on it for the
> >>>> Annual Report), if there's no reason why it should still be in stealth
> >>>> mode, I'd like to shout out about it from the rooftops.
> >>>> 
> >>>> Just let me know if we're good to go and if there are any
> >>>> disclaimers/caveats we should be aware of.
> >>>> 
> >>>> Warm thanks,
> >>>> Sally
> >>>> 
> >>>> 
> >>>> = = = = =
> >>>> vox +1 617 921 8656
> >>>> off2 +1 646 583 3362
> >>>> skype sallykhudairi

Re: svn commit: r1686683 - in /comdev/projects.apache.org/scripts: README.txt import/addpmc.py

[Hervé BOUTEMY]

ok, there is a misunderstanding: reverted as first step

then we need to discuss, since I don't see when it may be used given current 
logic where everything comes from committee-info.txt and rdf files: that's the 
way I added committees created during last monthes, ie simply running 
parsecommittees.py

adding committees as json when the committee does not exist in committee-
info.txt is a nonsense IMHO: once I added committe-info.txt parsing feature, 
after long thoughts on it, I really don't see any use for this addpmc.py 
script

(the discussion about RDF/DOAP is another independant topic, ie where to find 
information that is not in committee-info.txt)


do you really think addpmc.py is useful now?

Regards,

Hervé

Le dimanche 21 juin 2015 15:52:28 Daniel Gruno a écrit :
> Excuse me? That script WAS used for adding new committees to the site,
> simple and easy.
> Please revert, and don't just delete stuff because you personally don't
> use it.
> 
> WIth regards,
> Daniel.
> 
> On 2015-06-21 03:50, hbout...@apache.org wrote:
> > Author: hboutemy
> > Date: Sun Jun 21 01:50:14 2015
> > New Revision: 1686683
> > 
> > URL: http://svn.apache.org/r1686683
> > Log:
> > removed addpmc.py: not used
> > 
> > Removed:
> >  comdev/projects.apache.org/scripts/import/addpmc.py
> > 
> > Modified:
> >  comdev/projects.apache.org/scripts/README.txt
> > 
> > Modified: comdev/projects.apache.org/scripts/README.txt
> > URL:
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README.tx
> > t?rev=1686683&r1=1686682&r2=1686683&view=diff
> > =
> > = --- comdev/projects.apache.org/scripts/README.txt (original)
> > +++ comdev/projects.apache.org/scripts/README.txt Sun Jun 21 01:50:14 2015
> > 
> > @@ -34,8 +34,7 @@ various sources:
> > in: foundation/committees.json + foundation/committees-retired.json +
> > committee-info.txt
> > (https://svn.apache.org/repos/private/committers/board/committee-info
> > .txt) out: foundation/committees.json +
> > foundation/committees-retired.json> 
> > -- parsepmcs.py: imports PMC data (RDF) from the old project.apache.org
> > site. No need -  to run that more than once?
> > +- parsepmcs.py: imports PMC data (RDF) from the old project.apache.org
> > site.> 
> > in:
> > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/proj
> > ects/pmc_list.xml + PMC data .rdf files out: foundation/pmcs.json
> > 
> > @@ -43,8 +42,3 @@ various sources:
> > turns them into JSON objects.
> > in:
> > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/proj
> > ects/files.xml + projects' DOAP files out: projects/*.json +
> > foundation/projects.json
> > 
> > -
> > -- addpmc.py
> > -  in: foundation/pmcs.json + foundation/committees-evolution.json +
> > params
> > -  out: foundation/pmcs.json + foundation/committees-evolution.json
> > -  list of PMCs with site url (pmcs.json) and monthly list of new
> > committees (committees-evolution.json)

Re: Fw: Is https://projects-new.apache.org/ ready for prime time?

[Hervé BOUTEMY]

for me, the new site is ready: there is of course room for improvements, but 
it is stable and maintainable, waiting for contributions

notice: I changed the wording to stop using "TLP", but use "Committee" 
instead, since TLP cause issues when trying to describe each projects (the 
software) as TLP or sub-projects


when doing the switch, we'll need to rename current site as projects-
old.apache.org: there is some content to migrate (DOAP, documentation) 
associated to communication with projects on the changes that has to be 
decoupled from public vizualisation. I'll continue working on it.

There one choice to do: continue serving the pages from current VM or serve 
through standard resilient httpds. The VM is useful for cron jobs, but is not 
absolutely necessary for serving content since I removed online content 
editing that caused the VM requirement for content serving AFAIK. Using 
standard httpd will avoid SPOF or eventual load issue.


but definitely, the site is ready for the switch

Regards,

Hervé

Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit :
> Hello Uli and the Apache ComDev team --I hope this message finds you well.
> Per below, I'm interested in promoting the new Projects page.
> Can you please let me know if/when we're ready to do so?
> Thanks so much,
> Sally
> 
> - Forwarded Message -
>   From: David Nalley 
>  To: Sally Khudairi 
> Cc: Daniel Gruno ; ASF Infrastructure
>  Sent: Friday, June 19, 2015 11:50 AM
>  Subject: Re: Is https://projects-new.apache.org/ ready for prime time?
> 
> Hi Sally:
> 
> projects-new.apache.org is a ComDev managed resource, not an
> infrastructure managed resource. I think the PMC has had a discussion
> or two about when to migrate projects-new to projects.a.o
> 
> --David
> 
> 
> 
> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi
> 
>  wrote:
> > Hello Daniel and David --I hope you are both well.
> > 
> > 
> > I was wondering if the new Projects page at
> > 
> > https://projects-new.apache.org/
> > 
> > was ready to be publicly deployed/announced/promoted.
> > 
> > There's so much great information there and it's an incredible resource (I
> > use it every week for the News Round-ups and we relied on it for the
> > Annual Report), if there's no reason why it should still be in stealth
> > mode, I'd like to shout out about it from the rooftops.
> > 
> > Just let me know if we're good to go and if there are any
> > disclaimers/caveats we should be aware of.
> > 
> > Warm thanks,
> > Sally
> > 
> > 
> > = = = = =
> > vox +1 617 921 8656
> > off2 +1 646 583 3362
> > skype sallykhudairi

projects-new crontab

[Hervé BOUTEMY]

One step after the other :)

I updated cronjobs/parsereleases.py to improve releases.json generated content 
generated from /dist/
I also added the releases.json file to svn
http://svn.apache.org/viewvc/comdev/projects.apache.org/site/json/foundation/releases.json?view=log

But it seems there is a conflict since it doezs not appear on the site
https://projects-new.apache.org/json/foundation/ 
releases.json   2015-02-27 10:15219K 


How is this cron job managed? How can I update it, fix the conflict, and even 
change it since the code changed that much that I think some jobs should be 
removed and others added?

Regards,

Hervé

Re: permissions on COMDEV Wiki space

[Hervé BOUTEMY]

thank you Luciano: I confirm I was able to create content
https://cwiki.apache.org/confluence/display/COMDEV/Apache+Projects+Directory

Regards,

Hervé

Le dimanche 31 mai 2015 10:33:06 Luciano Resende a écrit :
> On Wed, May 27, 2015 at 11:43 PM, Hervé BOUTEMY 
> 
> wrote:
> > Hi,
> > 
> > Community Development has a Confluence Wiki space
> > https://cwiki.apache.org/confluence/display/COMDEV/Index
> > 
> > For projects-new.a.o, I'd like to use this Wiki to store some docs, but I
> > don't have karma.
> > 
> > Shouldn't this Wiki be opened to every ASF committer, like the svn space?
> > 
> > Regards,
> > 
> > Hervé
> 
> Done.

permissions on COMDEV Wiki space

[Hervé BOUTEMY]

Hi,

Community Development has a Confluence Wiki space
https://cwiki.apache.org/confluence/display/COMDEV/Index

For projects-new.a.o, I'd like to use this Wiki to store some docs, but I 
don't have karma.

Shouldn't this Wiki be opened to every ASF committer, like the svn space?

Regards,

Hervé

Re: projects-new.a.o updates

[Hervé BOUTEMY]

Le jeudi 21 mai 2015 11:38:05 sebb a écrit :
[...]
> > the only information that require manual entry is charter:
> So where is the charter to be documented?
"documented"?
I don't understand the question

if I look at http://projects.apache.org/docs/pmc.html, every field can be 
automatically filled with great precision (better precision than what people 
can do)
We just hav to decide where to write the remaining fields: there are a lot of 
svn places available
project.a.o then projects-new.a.o seems to be a good place to make information 
central and let PMCs know they're part of projects directory

the format question is just a detail (that has to be precised, of course)

[...]
> >> Might be easier to use a Wiki page for that?
> > 
> > it's temporary
> 
> Even more reason to use the Wiki, surely?
thinking at it, more than the About page, a Wiki could be a great place to put 
documentation for PMCs on the topic
then I just tried to find COMDEV wiki and use it
found, ok: https://cwiki.apache.org/confluence/display/COMDEV/Index
use, ko: how do I get karma?

Regards,

Hervé

Re: projects-new.a.o updates

[Hervé BOUTEMY]

Le mercredi 20 mai 2015 08:39:42 Sergio Fernández a écrit :
> Hi,
> 
> On Wed, May 20, 2015 at 12:52 AM, Hervé BOUTEMY 
> 
> wrote:
> > > One question Hervé, do all rdf files at
> > > https://projects-new.apache.org/doap/ are automatically generated or
> > 
> > copied
> > 
> > > from svn?
> > 
> > these ones are automatically generated from committer-info.txt by
> > parsecommittees.py
> > 
> > 
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/import/par
> > secommittees.py
> Perfect. I'll take a look there.
> 
> The first thing I'd like to change the way RDF files are generated.
> Generate RDF/XML with a XML library could look like a good idea, but
> actually it's a very bad one.  Valid XML files could be invalid RDF/XML. So
> i'd like to switch to RDFLib to generate those files. I'll provide a patch
> for internal validation.
don't hesitate to directly commit, it is easily reverted if there is a strong 
problem (which I don't epect: you're an Apache committer, isn't it?): since 
I'm not a RDF expert at all, and a noob in Python, starting with XML library 
was the easiest to start the work, hoping someone like you could improve (the 
way Daniel started the projects-new.a.o site and I jumped in to improve it 
with my own ideas)

> One idea that copuld show how the semantics goes
> beyond the syntax is to generated those DOAP files in other serializations,
> such as JSON-LD or Turtle. Then we'll slowly move into a more correct way.
> 
> Is that fine for you?
yes, great, thank you

> 
> what I still don't know is what is expected handwritten data in the PMC data
> > files
> > and if we really should try to generate such pmc.rdf files instead of
> > reading
> > content from
> > http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/p
> > mc_list.xml
> Well, the current file at
> http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/dat
> a/ contain only basic PMC information (name, homepage and chair), which I
> think we could get from LDAP or any other source.
> 
> The key concept I'd like to introduce here is that the less manually
> generated files the better for building a machine-drive infrastructure on
> top of them.
+1
the only question is: where do we get info that can't be discovered scraping 
existing information source (like committee-info.txt or LDAP)?
But any existing information extraction and reformatting has to be automated = 
parsecommittees.py

when you'll execute the script, you'll see that it checks consistency between 
different information sources and displays warnings when a discrepency is 
found: I think I'll add (if you don't beat me at it) the check against 
pmc_list.xml: the committee list at least should match, and if the committee 
name from PMC descriptor does not match what we have from committee(info.txt, 
we should warn

Regards,

Hervé

> 
> > I try to maintain ideas and comments in "Work in Progres" section of about
> > page: https://projects-new.apache.org/about.html
> 
> Ah, great!
> 
> Thanks.

Re: projects-new.a.o updates

[Hervé BOUTEMY]

Le mercredi 20 mai 2015 00:55:47 sebb a écrit :
> On 19 May 2015 at 23:52, Hervé BOUTEMY  wrote:
> > Le lundi 18 mai 2015 14:03:39 Sergio Fernández a écrit :
> >> Hi guys,
> >> 
> >> I have to admit I'm a bit lost with the development here; I do not have
> >> that much time, things change quite fast and discussions are a bit hard
> >> to
> >> follow. Hervé has done a great work; so some guidelines where I can
> >> contribute would help me a lot.
> >> 
> >> One question Hervé, do all rdf files at
> >> https://projects-new.apache.org/doap/ are automatically generated or
> >> copied
> >> from svn?
> > 
> > these ones are automatically generated from committer-info.txt by
> > parsecommittees.py
> > 
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/import/par
> > secommittees.py
> > 
> > what I still don't know is what is expected handwritten data in the PMC
> > data files
> 
> That is described here:
> 
> http://projects.apache.org/docs/pmc.html
yeah, I found and now understand: I tried to improve explanations to fix why I 
didn't understand explanations before (even if I read them multiple times) and 
was confused between projects DOAP files and committees PMC descriptor files

There are still confusing parts, IMHO:
- PMC entry under "DOAP Files" section
- "PMC descriptors" section in http://projects.apache.org/guidelines.html

But probably it's not really time to invest in projects.a.o since I hope we'll 
be able to switch to projects-new.a.o

I just added committee.html separate from project.html, and made different 
links for PMCs and projects:
https://projects-new.apache.org/projects.html?pmc

> 
> > and if we really should try to generate such pmc.rdf files instead of
> > reading content from
> > http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/
> > pmc_list.xml
> Most of the PMC data files are basic place-holders, but the syntax
> allows PMCs to create and maintain their own RDF files.
> 
> Do we really want to prevent them doing so?
the only information that require manual entry is charter: everything else can 
be automated, which will be easier and give better accuracy

> 
> Maybe the solution would be to ignore the dummy references such as
> 
> http://{tlp}.apache.org/"; />
yes, this dummy reference is a problem since it's "magic"

> 
> and instead generate the required info from other sources.
> 
> However, I don't know whether there is a canonical source for deriving
> the internal name and home page of a PMC from its full name
> e.g.
> Apache Portable Runtime => apr & http://apr.apache.org/
> Apache HttpComponents => httpcomponents & http://hc.apache.org/
> 
> There are other such examples where the conversion cannot readily be
> automated. [Except by maintaining a list of the exceptions somewhere]
I coded the few exceptions in the beginning of parsecommittees.py

Now we just need to define where to maintain the charter info, and generated 
pmc.rdf files from committee-info.txt + this charter will be the most accurate
and easy to find since it's a codified url: 
http://project-new.a.o/doap/{committee id}/pmc.rdf
Notice that I can improve parsecommittees.py to only update rdf files and not 
erase charter info but only update chair and PMC members

> 
> > I try to maintain ideas and comments in "Work in Progres" section of about
> > page: https://projects-new.apache.org/about.html
> 
> Might be easier to use a Wiki page for that?
it's temporary

Regards,

Hervé

> 
> > Regards,
> > 
> > Hervé
> > 
> >> Cheers,
> >> 
> >> On Sat, May 16, 2015 at 4:42 PM, sebb  wrote:
> >> > On 16 May 2015 at 08:22, Hervé BOUTEMY  wrote:
> >> > > Le samedi 16 mai 2015 00:36:03 sebb a écrit :
> >> > >> On 15 May 2015 at 22:08, Hervé BOUTEMY  
wrote:
> >> > >> > Le vendredi 15 mai 2015 14:02:52 sebb a écrit :
> >> > >> >> On 14 May 2015 at 23:38, Hervé BOUTEMY 
> >> > 
> >> > wrote:
> >> > >> >> > Hi,
> >> > >> >> > 
> >> > >> >> > I seriously updated content:
> >> > >> >> > - *every* TLP is listed, even when no DOAP file has been
> >> > >> >> > written
> >> > 
> >> > [1]
> >> > 
> >> > >> >> > - TLP project can be displayed, even without DOAP and provide
> >> > >> >> > link
> >> > 
> &

Re: projects-new.a.o updates

[Hervé BOUTEMY]

Le lundi 18 mai 2015 14:03:39 Sergio Fernández a écrit :
> Hi guys,
> 
> I have to admit I'm a bit lost with the development here; I do not have
> that much time, things change quite fast and discussions are a bit hard to
> follow. Hervé has done a great work; so some guidelines where I can
> contribute would help me a lot.
> 
> One question Hervé, do all rdf files at
> https://projects-new.apache.org/doap/ are automatically generated or copied
> from svn?
these ones are automatically generated from committer-info.txt by 
parsecommittees.py

http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/import/parsecommittees.py

what I still don't know is what is expected handwritten data in the PMC data 
files
and if we really should try to generate such pmc.rdf files instead of reading 
content from 
http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/pmc_list.xml

I try to maintain ideas and comments in "Work in Progres" section of about 
page: https://projects-new.apache.org/about.html

Regards,

Hervé

> 
> Cheers,
> 
> On Sat, May 16, 2015 at 4:42 PM, sebb  wrote:
> > On 16 May 2015 at 08:22, Hervé BOUTEMY  wrote:
> > > Le samedi 16 mai 2015 00:36:03 sebb a écrit :
> > >> On 15 May 2015 at 22:08, Hervé BOUTEMY  wrote:
> > >> > Le vendredi 15 mai 2015 14:02:52 sebb a écrit :
> > >> >> On 14 May 2015 at 23:38, Hervé BOUTEMY 
> > 
> > wrote:
> > >> >> > Hi,
> > >> >> > 
> > >> >> > I seriously updated content:
> > >> >> > - *every* TLP is listed, even when no DOAP file has been written
> > 
> > [1]
> > 
> > >> >> > - TLP project can be displayed, even without DOAP and provide link
> > 
> > to
> > 
> > >> >> > every
> > >> >> > sub-project [2]
> > >> >> > - when a TLP has a "main sub-project" with its DOAP file, data
> > 
> > from TLP
> > 
> > >> >> > and
> > >> >> > data from DOAP subproject are clearly separate [3]
> > >> >> 
> > >> >> The URLs [1] [2] [3] use the same namespace for PMCs and projects as
> > >> >> well as generic queries.
> > >> >> This may cause name clashes in future - e.g. a PMC called "numbers"
> > >> >> would clash with the "numbers" view of the data.
> > >> > 
> > >> > not exactly: [1] is project*s*.html while the 2 others are
> > 
> > project.html
> > 
> > >> > so no clash between projects listing type and project/PMC
> > >> 
> > >> Ah, OK, I'd not noticed the subtle difference.
> > >> 
> > >> However there is still a potential name clash: the Ant PMC is not the
> > >> same as the Ant project produced by the Ant PMC.
> > > 
> > > yes, even if Ant is one of the few committees that explicitely makes a
> > > difference between the committee and the project even if they share the
> > 
> > same
> > 
> > > name
> > > 
> > >> >> It would be better to use distinct namespaces for distinct types of
> > 
> > item.
> > 
> > >> > I don't think a clash between a PMC and a project can happen: if they
> > 
> > have
> > 
> > >> > the same id, it should be TLP's PMC, isn't it?
> > >> 
> > >> No, they are not the same thing.
> > >> A project is not a PMC, though they may have the same name.
> > >> 
> > >> A PMC is a group of people;
> > > 
> > > ok
> > > question: are committers a second group of people attached to a PMC?
> > 
> > Not always.
> > The committers LDAP groups are basically used to grant permission to
> > access code repos.
> > Not all PMCs use them, for example Subversion (and more recently
> > Commons) allow any ASF committer (another LDAP group) write access to
> > their source code.
> > 
> > Incubator committer groups are not defined in LDAP but have the same
> > purpose as the LDAP ones.
> > 
> > > To me,
> > > that's the case, even if some projects have their own committers list
> > 
> > (like
> > 
> > > incubator projects, or I suppose the lucene-* or hive-hcatalog or
> > 
> > xmlgraphics-
> > 
> > > fop & xmlgraphics-batik LDAP groups representing projects that didn't
> > 
> > write
> > 
> > > DOAP fi

Re: Project Visualization Tool...

[Hervé BOUTEMY]

Le samedi 16 mai 2015 00:30:55 sebb a écrit :
> On 15 May 2015 at 23:28, Hervé BOUTEMY  wrote:
> > Le vendredi 15 mai 2015 15:34:47 sebb a écrit :
> >> > I think we really have some data model problem here regarding what is a
> >> > "project's DOAP file": sometimes, a project is a PMC, sometimes a
> >> > project
> >> > is a deliverable, more like what is called in projectsnew.a.o a
> >> > "sub-project"
> >> 
> >> That is not how I understand DOAPs.
> >> 
> >> DOAP == Description Of A Project
> >> 
> >> i.e. some releaseable artifact.
> >> 
> >> A single PMC may have multiple projects, each with its own releases
> >> and repositories.
> >> These are modelled quite well in the DOAPs that PMCs have created.
> > 
> > +1
> > 
> >> Information about the PMC which manages the projects is NOT stored in
> >> a DOAP, it is stored in a PMC data file.
> >> This is referenced from a DOAP using
> >> 
> >> 
> >> 
> >> where URL is either an actual URL of a PMC data file or a dummy URL e.g.
> >> 
> >> 
> >> 
> >> which leads to a file here:
> >> 
> >> https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects
> >> /da ta_files/.rdf
> > 
> > I'm not RDF expert, but this Apache-specific algorithm to find PMC rdf
> > file seems strange: I understand it is coded/known from projects.a.o xslt
> > transformation
> Yes.
> 
> > But this should be usable from any RDF tooling, no?
> 
> It's not currently usable except by using special processing.
> 
> The problem is that the shorthand URL is used by all but about 4 of
> the PMCs, so it would be a major challenge to get this fixed.
> 
> Some PMCs are quick to fix such issues; some may take weeks or months
> to fix even a simple error.
I think that people don't understand this PMC information rdf file (I didn't 
until our current discussion)
But with good explanations and visualization help given by projects-new.a.o, 
we can go really faster: I'm ready to try once we're clear :)

> 
> > Another problem I see with these PMC data rdf files is that they seem to
> > not be really maintained: I doubt PMCs update PMC data rdf files on each
> > PMC Chair change.
> 
> Yes.
> 
> > That's why I had the idea of generating/updating the chair when
> > parsing committee-info.txt.
> 
> Fair enough, but that does not mean the code needs to create yet
> another RDF file.
+1
my itend was not to create a new one, but replace with generated info

> 
> > But other information manually written in current PMC data rdf files can't
> > be found anywhere else, AFAIK.
> 
> Yes.
that's where it hurst: we need to mix handwritten with generated content... 
nedd to be clear on the process

> 
> > Last problem: I personnally really didn't understand this PMC data rdf
> > file
> > until now. I don't know who understands it :)
> > IMHO, the magic algorithm to find the rdf file is a root cause.
> 
> The PMC data file is documented here:
> 
> http://projects.apache.org/docs/pmc.html
yeah, I read it several time before, I knew I was not confident with what I 
read, and now I know I completely misread it until now.

> 
> >> > if you look at https://projects-new.apache.org/projects.html?pmc,
> >> > typical
> >> > cases for that are:
> >> > - Incubator: there is the "the Incubator project", displayed without
> >> > DOAP
> >> > file since the incubator has special source info, and many sub-projects
> >> > which provide DOAP files
> >> > - Commons: there is no "Commons' DOAP file", then no TLP... on
> >> > sub-project
> >> > is quasi randomly chosen... Common's DOAP file, if it existed would not
> >> > release anything, it"s a pure "organizational" project
> >> 
> >> There is an ambiguity here: project can mean an organisational entity
> >> and project can mean a releaseable artifact.
> >> 
> >> There are different RDF files for the two meanings; only the artifact
> >> has an associated DOAP.
> >> 
> >> > - Ant: there is an Ant DOAP file that represent the TLP and the main
> >> > released artifact
> >> 
> >> No, it only links to the TLP = PMC data file, it does not represent the
> >> TLP. The Ant DOAP file only represents the Ant product.
> > 
> > ok, IIUC, I shou

Re: projects-new.a.o updates

[Hervé BOUTEMY]

Le samedi 16 mai 2015 00:36:03 sebb a écrit :
> On 15 May 2015 at 22:08, Hervé BOUTEMY  wrote:
> > Le vendredi 15 mai 2015 14:02:52 sebb a écrit :
> >> On 14 May 2015 at 23:38, Hervé BOUTEMY  wrote:
> >> > Hi,
> >> > 
> >> > I seriously updated content:
> >> > - *every* TLP is listed, even when no DOAP file has been written [1]
> >> > - TLP project can be displayed, even without DOAP and provide link to
> >> > every
> >> > sub-project [2]
> >> > - when a TLP has a "main sub-project" with its DOAP file, data from TLP
> >> > and
> >> > data from DOAP subproject are clearly separate [3]
> >> 
> >> The URLs [1] [2] [3] use the same namespace for PMCs and projects as
> >> well as generic queries.
> >> This may cause name clashes in future - e.g. a PMC called "numbers"
> >> would clash with the "numbers" view of the data.
> > 
> > not exactly: [1] is project*s*.html while the 2 others are project.html
> > so no clash between projects listing type and project/PMC
> 
> Ah, OK, I'd not noticed the subtle difference.
> 
> However there is still a potential name clash: the Ant PMC is not the
> same as the Ant project produced by the Ant PMC.
yes, even if Ant is one of the few committees that explicitely makes a 
difference between the committee and the project even if they share the same  
name

> 
> >> It would be better to use distinct namespaces for distinct types of item.
> > 
> > I don't think a clash between a PMC and a project can happen: if they have
> > the same id, it should be TLP's PMC, isn't it?
> 
> No, they are not the same thing.
> A project is not a PMC, though they may have the same name.
> 
> A PMC is a group of people;
ok
question: are committers a second group of people attached to a PMC? To me, 
that's the case, even if some projects have their own committers list (like 
incubator projects, or I suppose the lucene-* or hive-hcatalog or xmlgraphics-
fop & xmlgraphics-batik LDAP groups representing projects that didn't write 
DOAP file)
see http://people.apache.org/committers-by-project.html

I suppose we could display the difference when some projects have their own 
committers list that is different from the TLP's committers list

> a project is a software artifact.
ok,
that's the classical way IT people talk, even if that's not the way business 
people talk: I think this is a cause for major misunderstandings between devs 
and business, but that's a larger problem than ASF's internals we're working 
on :)

what is confusing, IMHO, is that we tell that a TLP == a PMC
and a PMC != projects
then a TLP != project: which in full words is "a Top Level Project is not a 
project": confusing


I'll create committee.html to display PMC (or "TLP") information and let 
projects link to the committee: that should be easy to do and revert if we're 
not happy with the result

notice that https://projects-new.apache.org/projects.html?pmc is confusing 
with this definition in place: TLP (ie PMC with our definition) icons are 
displayed against projects
If not too risky, I'll update this part too when trying committee.html


one good thing with committee.html is that we'll be able to display special 
committees

> 
> >> > This makes more clear what DOAP is used for (and why we need projects
> >> > hand-
> >> > writing some data, but not everything)
> >> > 
> >> > I didn't update target doap urls [4] since I don't know what precisely
> >> > to
> >> > do: copy doap files that were processed, in appropriate directory, and
> >> > with consistent filename than generated json?
> >> 
> >> What are the target DOAP files used for?
> > 
> > I don't know: I coded what I understood from discussion with Sergio
> > Fernández But I admit I don't really know if this is a good idea or not
> > 
> >> Where do they originate?
> > 
> > {tlp-id}/pmc.rdf is generated with info parsed from committee-info.txt by
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/import/par
> > secommittees.py?view=markup (with the help of
> > http://www.apache.org/#projects-list scraped info for short description)
> > 
> > And the idea behind rdf copy was just to copy files in a uniform location
> > from
> > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects
> > /files.xml to ease DOAP finding just an idea
> > 
> > Regards,
> > 
> > Hervé
> > 
> >> > Feedback expected :)
> >> > 
> >> > Regards,
> >> > 
> >> > Hervé
> >> > 
> >> > 
> >> > [1] https://projects-new.apache.org/projects.html?pmc
> >> > 
> >> > [2] https://projects-new.apache.org/project.html?commons
> >> > 
> >> > [3] https://projects-new.apache.org/project.html?ant
> >> > 
> >> > [4] https://projects-new.apache.org/doap/

Re: Project Visualization Tool...

[Hervé BOUTEMY]

Le vendredi 15 mai 2015 15:34:47 sebb a écrit :
> > I think we really have some data model problem here regarding what is a
> > "project's DOAP file": sometimes, a project is a PMC, sometimes a project
> > is a deliverable, more like what is called in projectsnew.a.o a
> > "sub-project"
> That is not how I understand DOAPs.
> 
> DOAP == Description Of A Project
> 
> i.e. some releaseable artifact.
> 
> A single PMC may have multiple projects, each with its own releases
> and repositories.
> These are modelled quite well in the DOAPs that PMCs have created.
+1

> Information about the PMC which manages the projects is NOT stored in
> a DOAP, it is stored in a PMC data file.
> This is referenced from a DOAP using
> 
> 
> 
> where URL is either an actual URL of a PMC data file or a dummy URL e.g.
> 
> 
> 
> which leads to a file here:
> 
> https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/da
> ta_files/.rdf
I'm not RDF expert, but this Apache-specific algorithm to find PMC rdf file 
seems 
strange: I understand it is coded/known from projects.a.o xslt transformation
But this should be usable from any RDF tooling, no?

Another problem I see with these PMC data rdf files is that they seem to not be 
really maintained: I doubt PMCs update PMC data rdf files on each PMC Chair 
change. That's why I had the idea of generating/updating the chair when 
parsing committee-info.txt.
But other information manually written in current PMC data rdf files can't be 
found anywhere else, AFAIK.

Last problem: I personnally really didn't understand this PMC data rdf file 
until now. I don't know who understands it :)
IMHO, the magic algorithm to find the rdf file is a root cause.

> > if you look at https://projects-new.apache.org/projects.html?pmc, typical
> > cases for that are:
> > - Incubator: there is the "the Incubator project", displayed without DOAP
> > file since the incubator has special source info, and many sub-projects
> > which provide DOAP files
> > - Commons: there is no "Commons' DOAP file", then no TLP... on sub-project
> > is quasi randomly chosen... Common's DOAP file, if it existed would not
> > release anything, it"s a pure "organizational" project
> 
> There is an ambiguity here: project can mean an organisational entity
> and project can mean a releaseable artifact.
> 
> There are different RDF files for the two meanings; only the artifact
> has an associated DOAP.
> 
> > - Ant: there is an Ant DOAP file that represent the TLP and the main
> > released artifact
> 
> No, it only links to the TLP = PMC data file, it does not represent the TLP.
> The Ant DOAP file only represents the Ant product.
ok, IIUC, I should rephrase https://projects-new.apache.org/project.html?ant : 
1. "Top Level Project data:" to "Apache Committee data:"
2. "Project established:" to "Committee established:"
3. "Sub-projects (8):" to "Projects (8):", eventually boldening the TLP if one 
is the TLP

and I should rename tlps.json to committees.json (and update code accordingly)

then on https://projects-new.apache.org/ , do we really want to graph TLPs 
evolution or committees?
I suppose commons can be called a TLP, even if it does not have any "main" 
project that is the effective TLP
comdev is not really a TLP: should probably not be listed in projects list, 
but as "special committee not producing projects"?
is Labs a TLP? or like comdev?
I suppose we can hard-code the list of committees that are not expected to 
have projects, the list should not change often: Labs and comdev seem to be 
the only 2 (that extend special committees from 5 to 7)

and finally, in https://projects-new.apache.org/
change "163 top level software projects
107 sub-projects" to "270 projects managed by 163 committees" (or 161 if labs 
and comdev are special committees)


this seems to make sense
if no objection, I'll code it

Regards,

Hervé

> 
> > I chose Commons, but it could have been HttpComponents or Logging
> > Services, or Lucene (Lucene have been very clear that there is a "Lucene
> > core" sub- project), Web Services, Axis, Xalan, Xerces, XML Graphics,
> > Attic, Creadur, DB, jUDDI, Tcl
> > 
> > I chose Ant, but it could have been Velocity, MINA, Directory, HTTP
> > Server,
> > MyFaces, Tomcat
> > 
> >> - (future) UI additions for *other* places.  It would be awesome, for
> >> example, to provide a tiny scriptlet that any project could inject in
> >> their website that displays a "see also" menu.  That would link to a
> >> specific URL on projects.a.o that would say "hey, you came from
> >> Cassandra, here are: -other big data projects, -other projects in Java,
> >> -other projects with the same committers... etc." as a service.
> >> 
> >> - Shane
> > 
> > I'll continue tonight on this
> > Any help appreciated
> > 
> > Regards,
> > 
> > Hervé

Re: projects-new.a.o updates

[Hervé BOUTEMY]

Le vendredi 15 mai 2015 14:02:52 sebb a écrit :
> On 14 May 2015 at 23:38, Hervé BOUTEMY  wrote:
> > Hi,
> > 
> > I seriously updated content:
> > - *every* TLP is listed, even when no DOAP file has been written [1]
> > - TLP project can be displayed, even without DOAP and provide link to
> > every
> > sub-project [2]
> > - when a TLP has a "main sub-project" with its DOAP file, data from TLP
> > and
> > data from DOAP subproject are clearly separate [3]
> 
> The URLs [1] [2] [3] use the same namespace for PMCs and projects as
> well as generic queries.
> This may cause name clashes in future - e.g. a PMC called "numbers"
> would clash with the "numbers" view of the data.
not exactly: [1] is project*s*.html while the 2 others are project.html
so no clash between projects listing type and project/PMC

> It would be better to use distinct namespaces for distinct types of item.
I don't think a clash between a PMC and a project can happen: if they have the 
same id, it should be TLP's PMC, isn't it?

> 
> > This makes more clear what DOAP is used for (and why we need projects
> > hand-
> > writing some data, but not everything)
> > 
> > I didn't update target doap urls [4] since I don't know what precisely to
> > do: copy doap files that were processed, in appropriate directory, and
> > with consistent filename than generated json?
> 
> What are the target DOAP files used for?
I don't know: I coded what I understood from discussion with Sergio Fernández
But I admit I don't really know if this is a good idea or not

> Where do they originate?
{tlp-id}/pmc.rdf is generated with info parsed from committee-info.txt by 
http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/import/parsecommittees.py?view=markup
 
(with the help of http://www.apache.org/#projects-list scraped info for short 
description)

And the idea behind rdf copy was just to copy files in a uniform location from 
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml
 to ease DOAP finding
just an idea

Regards,

Hervé

> 
> > Feedback expected :)
> > 
> > Regards,
> > 
> > Hervé
> > 
> > 
> > [1] https://projects-new.apache.org/projects.html?pmc
> > 
> > [2] https://projects-new.apache.org/project.html?commons
> > 
> > [3] https://projects-new.apache.org/project.html?ant
> > 
> > [4] https://projects-new.apache.org/doap/

Re: projects-new.a.o updates

[Hervé BOUTEMY]

thank you :)

now, comdev is visible, without writing a DOAP

https://projects-new.apache.org/project.html?comdev

Regards,

Hervé

Le vendredi 15 mai 2015 08:54:50 Rich Bowen a écrit :
> On 05/14/2015 06:38 PM, Hervé BOUTEMY wrote:
> > Feedback expected:)
> 
> You rock.

Re: projects-new.a.o updates

[Hervé BOUTEMY]

ok, fixed: this was caused by the fact that org LDAP group has not yet been 
created
algorithm changed to handle that case: if any other display is wrong, please 
report

Regards,

Hervé

Le jeudi 14 mai 2015 17:17:46 Owen O'Malley a écrit :
> Orc is listed as retired instead of active.
> 
> .. Owen
> 
> > On May 14, 2015, at 15:38, Hervé BOUTEMY  wrote:
> > 
> > Hi,
> > 
> > I seriously updated content:
> > - *every* TLP is listed, even when no DOAP file has been written [1]
> > - TLP project can be displayed, even without DOAP and provide link to
> > every
> > sub-project [2]
> > - when a TLP has a "main sub-project" with its DOAP file, data from TLP
> > and
> > data from DOAP subproject are clearly separate [3]
> > This makes more clear what DOAP is used for (and why we need projects
> > hand-
> > writing some data, but not everything)
> > 
> > I didn't update target doap urls [4] since I don't know what precisely to
> > do: copy doap files that were processed, in appropriate directory, and
> > with consistent filename than generated json?
> > 
> > Feedback expected :)
> > 
> > Regards,
> > 
> > Hervé
> > 
> > 
> > [1] https://projects-new.apache.org/projects.html?pmc
> > 
> > [2] https://projects-new.apache.org/project.html?commons
> > 
> > [3] https://projects-new.apache.org/project.html?ant
> > 
> > [4] https://projects-new.apache.org/doap/

projects-new.a.o updates

[Hervé BOUTEMY]

Hi,

I seriously updated content:
- *every* TLP is listed, even when no DOAP file has been written [1]
- TLP project can be displayed, even without DOAP and provide link to every 
sub-project [2]
- when a TLP has a "main sub-project" with its DOAP file, data from TLP and 
data from DOAP subproject are clearly separate [3]
This makes more clear what DOAP is used for (and why we need projects hand-
writing some data, but not everything)

I didn't update target doap urls [4] since I don't know what precisely to do: 
copy doap files that were processed, in appropriate directory, and with 
consistent filename than generated json?

Feedback expected :)

Regards,

Hervé


[1] https://projects-new.apache.org/projects.html?pmc

[2] https://projects-new.apache.org/project.html?commons

[3] https://projects-new.apache.org/project.html?ant

[4] https://projects-new.apache.org/doap/

Re: DOAP format question

[Hervé BOUTEMY]

I started generating /doap/{tlp-id}/pmc.rdf
Please tell me what to add in these files

I don't understand what to write into /doap/foundation/tlps.rdf

And for /doap/{tlp-id}/{project-id}.rdf, the content can't be generated: there 
is a lot of handwritten content we can't guess automatically
What we can do is copying projects hadcrafted content to the structured 
location: but even extracting the {project-id} is not easy

any idea?

Regards,

Hervé

Le mardi 12 mai 2015 18:23:12 Sergio Fernández a écrit :
> Hi,
> 
> On Tue, May 12, 2015 at 8:47 AM, Hervé BOUTEMY 
> 
> wrote:
> > I think we could generate an authoritative DOAP url for TLPs from
> > committee-
> > info.txt
> > then give instructions to projects to update their software DOAP files to
> > point
> > to these reference TLPs DOAP files
> 
> Exactly. I think a conclusion we could arrive with the years using DOAP
> files in ASF is simple: handcrafted files are
> 
> So I think the goal for projects-new.apache.org would be to automatically
> generate the DOAP files, including: TLPs (PMCs), projects and releases. We
> have that data somewhere (LDAP?), I'm pretty sure, we just need to get it
> and process it.
> 
> > I can generate tonight http://projects-new.apache.org/doap/tlp/ as a POC
> > for
> > 
> > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/
> > data_files replacement
> 
> OK, bootstrap it, and then I'll jump it to do the proper RDF coding there.
> 
> I'll propose to publish at least:
> 
>   1) /doap/foundation/tlps.rdf
>   2) /doap/{tlp-id}/pmc.rdf
>   3) /doap/{tlp-id}/{project-id}.rdf
> 
> 1 will provide the basic information, linking to 2 containing the pmc
> information, as we already do in json. Then 3 would also link to 2, where
> in most of the cases {tlp-id} and {project-id} will be the same, but we do
> support subprojects (e.g., lucene) and components (e.g., commons).
> 
> One we have that infrastructure in place, we can tell all TLPs to directly
> link to those files, avoiding the manual duplication of that data.
> 
> I think with that we are coming closer to a satisfactory solution ;-)

Re: DOAP format question

[Hervé BOUTEMY]

Le lundi 11 mai 2015 08:46:41 Sergio Fernández a écrit :
> Hi sebb,
> 
> On Tue, May 5, 2015 at 7:08 PM, sebb  wrote:
> > > What I can already say is that I do not understand what
> > 
> > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/
> > data_files> 
> > > aim to represent.
> > 
> > This is the default location for the PMC data [1] files which provide
> > data about the PMC.
> > A single such file may be referenced by multiple DOAPs.
> > E.g. all the Commons components refer to the same PMC data file.
> 
> I do understand how DOAP is being used, and I guess it has been wrong from
> the very beginning.
I fear that's true :/
let's analyze what is wrong and fix it :)

> 
> Taking commons-lang as example, they currently have:
> 
>   http://commons.apache.org/lang/";>
> http://commons.apache.org/"/>
>   
> 
> which does not really link (in RDF) to the file
> https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/da
> ta_files/commons.rdf
> 
> RDF is a directly-label graph data model that uses URIs as names. Therefore
> the URI you put as as value of a property has a meaning, you should be able
> to directly fetch it, but not having such implicit rules where files a
> located in a svn. I guess apply that would mean a major restructuration of
> the current DOAP data, but that's something I can help to do to all PMCs.
> 
> Beside that issue on linking, I have come to the conclusions that asfext
> actually have the sense of two things:
> 
> * asfext:pmc is the property that links a project with its PMC
> * asfext:PMC should be a class for referring to PMCs
> 
> And that completely valid, but the tooling should know the difference and
> not just try to fix wrong data.
while working on it, I think I found one root cause: we're not clear about 
TLPs (with PMCs) vs software (often called "projects" too, but that have 
releases)

it seems 
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files
 is about TLPs/PMCs
and "classical" DOAP files written by people are about softwares that are done 
by TLPs/PMCs

We have a TLPs/PMCs authoritative source of information: that is committee-
info.txt
I used it as main source of data for
https://projects-new.apache.org/json/foundation/tlps.json
The only informations in tlps.json that do not come from committee-info.txt 
are:
- committers list (committee-info.txt only lists PMC members, LDAP gives 
committers)
- description of the TLPs: I'm still looking which could be the authoritative 
information source

for more details, the parsing code is here:
http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/import/parsecommittees.py?view=markup

I think we could generate an authoritative DOAP url for TLPs from committee-
info.txt
then give instructions to projects to update their software DOAP files to point 
to these reference TLPs DOAP files

this would:
- fix issues regarding standard DOAP/RDF semantics
- be easy to explain

I can generate tonight http://projects-new.apache.org/doap/tlp/ as a POC for 
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files
 replacement

notice: from TLP and PMC, I prefer to talk about TLP, since the TLP has a PMC 
+ a homepage, committers, and other attributes

WDYT?

Regards,

Hervé

> 
> Let me try to find some time to put some of these things in order to have a
> better overview...

Re: Standards for mail archive statistics gathering?

[Hervé BOUTEMY]

Le mercredi 6 mai 2015 12:48:34 Steve Blackmon a écrit :
> > For visualization, for sure, json is the current natural format when data
> > is consumed from the browser.
> > I don't have great experience on this, and what I'm missing with json
> > currently is a common practice on documenting a structure: are there
> > common
> > practices?
> 
> In podling streams [0], we make extensive use of json schema [1]
thank you: that's exactly the initial info I was looking for: json schema!

> from
> which we generate POJOs with a maven
> plugin jsonschema2pojo [2] which makes manipulating the objects in
> Java/Scala pleasant.  I expect other languages have
> similar jsonschema-based ORM paradigms as well.
As usual Java devloper, your tooling is interesting
But in the projects-new.a.o case, it is data extraction is coded in Python: if 
we create json schema, having Python classes generated could simplify coding.
Anyone with Python+json schema experience around?


> This pattern supports
> inheritance both within
> and across projects - for example see how [3] extends [4] which
> extends [5].  These schemas are relatively self documenting,
> but generating documentation or other artifacts is straight-forward as
> they are themselves json documents.
yeah, json schema document is easy to read (at least the examples on the 
site...)

> 
> > Because for simple json structure, documentation is not really necessary,
> > but once the structure goes complex, documentation is really a key
> > requirement for people to use or extend. And I already see this
> > shortcoming with the 11 json files from projects-new.a.o =
> > https://projects-new.apache.org/json/foundation/
> Having used these json documents a few weeks ago to build an apache
> community visualization [6]
yeah, really nice visualization!

> IMO the current crop of project-new jsons
> are intermediate artifacts rather than a sufficiently cross-purpose
> data model, a role currently held by DOAP mbox and misc others all
> with some inherent shortcomings most notably lack of navigability
> between silos.
+1
I'm at a point where I start to really understand the concepts involved and 
want to code a simple data model: I'll report here once I have a first version 
available.

> I'd like to nominate activity streams [7] with
> community-specific extensions (such as those roughly prototyped here:
> [8] ) as a potential core data model for this effort going forward
I had a first look at it: it is more complex than what I had in mind
We'll have to share and see what's the best bet

> and
> I'm happy to help apply some of the useful tools and connectors within
> podling streams toward that end. Converting external structured
> sources into normalized documents and indexing those activities to
> power data-centric APIs and visualizations are wheelhouse use cases
> for this project, as they say.
Great, stay tuned: I'll probably work on it this week-end

Regards,

Hervé

> 
> [0] http://streams.incubator.apache.org/
> [1] http://json-schema.org/documentation.html
> [2] http://www.jsonschema2pojo.org/
> [3]
> https://github.com/steveblackmon/streams-apache/blob/master/activities/src/
> main/jsonschema/objectTypes/committee.json [4]
> https://github.com/apache/incubator-streams/blob/master/streams-pojo/src/ma
> in/jsonschema/objectTypes/group.json [5]
> https://github.com/apache/incubator-streams/blob/master/streams-pojo/src/ma
> in/jsonschema/object.json [6] http://72.182.111.65:3000/workspace/3
> [7] http://activitystrea.ms/
> [8]
> https://github.com/steveblackmon/streams-apache/blob/master/activities/src/
> main/jsonschema
> 
> Steve Blackmon
> sblack...@apache.org
> 
> On Wed, May 6, 2015 at 2:05 AM, Hervé BOUTEMY  wrote:
> > Le mardi 5 mai 2015 21:26:36 Shane Curcuru a écrit :
> >> On 5/5/15 7:33 AM, Boris Baldassari wrote:
> >> > Hi Folks,
> >> > 
> >> > Sorry for the late answer on this thread. Don't know what has been done
> >> > since then, but I've some experience to share on this, so here are my
> >> > 2c..
> >> 
> >> No, more input is always appreciated!  Hervé is doing some
> >> centralization of the projects-new.a.o data capture, which is related
> >> but slightly separate.
> > 
> > +1
> > this can give a common place to put code once experiments show that we
> > should add a new data source
> > 
> >> But this is going to be a long-term project
> > 
> > +1
> > 
> >> with
> >> plenty of different people helping I bet.
> > 
> > I hope so...
> > 
> >> ...
> >> 
> >> &

Re: Standards for mail archive statistics gathering?

[Hervé BOUTEMY]

Le mardi 5 mai 2015 21:26:36 Shane Curcuru a écrit :
> On 5/5/15 7:33 AM, Boris Baldassari wrote:
> > Hi Folks,
> > 
> > Sorry for the late answer on this thread. Don't know what has been done
> > since then, but I've some experience to share on this, so here are my 2c..
> 
> No, more input is always appreciated!  Hervé is doing some
> centralization of the projects-new.a.o data capture, which is related
> but slightly separate.
+1
this can give a common place to put code once experiments show that we should 
add a new data source

> But this is going to be a long-term project
+1

> with
> plenty of different people helping I bet.
I hope so...

> 
> ...
> 
> > * Parsing mboxes for software repository data mining:
> > There is a suite of tools exactly targeted at this kind of duty on
> > github: Metrics Grimoire [1], developed (and used) by Bitergia [2]. I
> > don't know how they manage time zones, but the toolsuite is widely used
> > around (see [3] or [4] as examples) so I believe they are quite robust.
> > It includes tools for data retrieval as well as visualisation.
> 
> Drat.  Metrics Grimoire looks pretty nifty - essentially a set of
> frameworks for extracting metadata from a bunch of sources - but it's
> GPL, so personally I have no interest in working on it.  If someone else
> uses it to generate datasets that's great.
> 
> > * As for the feedback/thoughts about the architecture and formats:
> > I love the REST-API idea proposed by Rob. That's really easy to access
> > and retrieve through scripts on-demand. CSV and JSON are my favourite
> > formats, because they are, again, easy to parse and widely used -- every
> > language and library has some facility to read them natively.
> 
> Yup - again, like project visualization, to make any of this simple for
> newcomers to try stuff, we need to separate data gathering / model /
> visualization.  Since most of these are spare time projects, having easy
> chunks makes it simpler for different people to try their hand at it.
For visualization, for sure, json is the current natural format when data is 
consumed from the browser.
I don't have great experience on this, and what I'm missing with json 
currently is a common practice on documenting a structure: are there common 
practices?
Because for simple json structure, documentation is not really necessary, but 
once the structure goes complex, documentation is really a key requirement for 
people to use or extend. And I already see this shortcoming with the 11 json 
files from projects-new.a.o = https://projects-new.apache.org/json/foundation/

Regards,

Hervé

> 
> Thanks,
> 
> - Shane

Re: Project Visualization Tool...

[Hervé BOUTEMY]

Le samedi 18 avril 2015 10:55:00 Shane Curcuru a écrit :
> LOL, below.
> 
> I highly recommend separating the model from the views, so that we can
> efficiently enable our volunteer's energy here to actually accomplish
> something valuable.
+1

> 
> So let's work on stuff to do that excites us, but remember to keep the
> technical problems focused on what this PMC believes we can truly create
> and maintain going forward.
> 
> Don't worry about everything at once.  Just focus on separate bits:
> 
> - Method to scrape source data from our various definitive or even not
> completely definitive but very close places (txt files, websites, LDAP)
> 
> - Model and data source that actually holds info about committer lists
> and project metadata.  I'm betting Daniels' projects-new does this very
> well already.
+1 it's a perfect starting point: just need to document and continue to 
improve
then I started by documenting what are the current information sources used 
for generating projects-new.a.o json files:
see https://projects-new.apache.org/json/foundation/ and 
http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README.txt?view=markup

> 
> --
> - Stable API to get at that model.  Would be really nice if we did this
> just once, so that people working above here don't interfere with people
> working below here.
> --
+1

Since there are multiple information sources for TLPs/PMCs/committers, I think 
I will consolidate to avoid what's currently happenning: the projects.js (ie 
one visualization) contains a lot of code to consolidate the multiple 
information sources
If the consolidation is done server side, in the generation scripts, it will 
be easier to use for projects.js and any other tool wanting to do other future 
visualizations

> 
> - Visualizations.  There's lots of different stuff to do here, and I
> think it'd be super helpful if everyone just did something they want,
> and then show us the code.
+1

> 
> Sure, there's lots of "what is important" to focus on, but I for one
> would love to see real examples of all the cool visualization libraries
> out there, and I know a couple folks already use some of them.
> 
> - UI additions for the projects-new/projects websites, which are
> featured at the top level of a.o.  I.e., this is our "projects
> directory", how can we better lead people who arrive there at what they
> want to know?
at the moment, I'm not trying to add any new UI, but improve the consistency 
of displayed data, since current state is not really consistent: some PMCs are 
not displayed, probably because they have not provided any DOAP file. But even 
without DOAP file, we have a lot of data to display for a TLP, most of what we 
display for a TLP (ie a project that does not have any subproject)

I think we really have some data model problem here regarding what is a 
"project's DOAP file": sometimes, a project is a PMC, sometimes a project is a 
deliverable, more like what is called in projectsnew.a.o a "sub-project"

if you look at https://projects-new.apache.org/projects.html?pmc, typical 
cases for that are:
- Incubator: there is the "the Incubator project", displayed without DOAP file 
since the incubator has special source info, and many sub-projects which 
provide DOAP files
- Commons: there is no "Commons' DOAP file", then no TLP... on sub-project is 
quasi randomly chosen... Common's DOAP file, if it existed would not release 
anything, it"s a pure "organizational" project
- Ant: there is an Ant DOAP file that represent the TLP and the main released 
artifact

I chose Commons, but it could have been HttpComponents or Logging Services, or 
Lucene (Lucene have been very clear that there is a "Lucene core" sub-
project), Web Services, Axis, Xalan, Xerces, XML Graphics, Attic, Creadur, DB, 
jUDDI, Tcl

I chose Ant, but it could have been Velocity, MINA, Directory, HTTP Server, 
MyFaces, Tomcat


> 
> - (future) UI additions for *other* places.  It would be awesome, for
> example, to provide a tiny scriptlet that any project could inject in
> their website that displays a "see also" menu.  That would link to a
> specific URL on projects.a.o that would say "hey, you came from
> Cassandra, here are: -other big data projects, -other projects in Java,
> -other projects with the same committers... etc." as a service.
> 
> - Shane

I'll continue tonight on this
Any help appreciated

Regards,

Hervé

Re: DOAP format question

[Hervé BOUTEMY]

Le mardi 5 mai 2015 01:05:31 sebb a écrit :
> > OK, but that's because whoever code the XSLT decided to be defensive to
> > such interpretation.
> 
> If you read back in this thread you will see that I did this in order
> to support both asfext:PMC and asfext:pmc.
> 
> > But that does not mean is right.
> 
> The code is right in the sense that it works with the input files that
> are provided.
+1
that's a temporary workaround that we should try to not need any more in the 
future

[...]

> >> Also if it is possible to validate that the various RDF files are
> >> correct according to the formal definitions.
> >> PMCs could then submit their files for checking.
> > 
> > I think we can discuss that infrastructure for the new site. I'm happy to
> > help. Python provides the required libraries. I'll open a thread, probably
> > tomorrow.
> 
> I think there needs to be a way for PMCs to check their RDF files
> against the formal definitions.
> For example, a CGI script that accepts the URL of a file.
+1
I tried W3C checker, but as it is only a syntax checker, it checked only 
syntax, not references to the namespace
and I couldn't find any other useful tool :(

Other tools to make effective use of the DOAP files would be useful too: but I 
completely agree that the first priority seems to have a more complete checker

Regards,

Hervé

> 
> > Cheers,
> > 
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co

Re: DOAP format question

[Hervé BOUTEMY]

I'm not a RDF expert: if someone with more knowledge on this can join, it 
would be really useful

But apart from seeing that most of the documentation was talking about pmc 
instead of PMC [1] (I just had to fix 1 place), I was convinced that the 
correct case is lowercase when reading asfext definition [2]
once again, I'm not an expert then could misinterpret the content, but I read 
http://projects.apache.org/ns/asfext#pmc";> as a 
definition of pmc field, in lowercase


since I was working on projects-new.a.o, I completely forgot to try to 
generate the current projects.a.o to check that the change didn't break 
anything: sorry, I'll try it tonight

one question: where is the cron log of the effective run?

Regards,

Hervé


[1] http://projects.apache.org/docs/pmc.html

[2] http://projects.apache.org/ns/asfext

Le lundi 4 mai 2015 01:39:45 sebb a écrit :
> XPath nodes are case-sensitive;  is not the same as
> .
> 
> The change from PMC to pmc has broken some of the reports - the PMC
> name is missing from most of the entries listed in
> http://projects.apache.org/indexes/pmc.html.
> 
> I don't know which case is correct, but there are currently RDF files
> in project repos which use PMC rather than pmc.
> These files are not easy to fix, as each project has to be asked to do them.
> 
> I can probably fix the scripts to check for both, but that is quite messy.
> 
> It would be better to use the "correct" case setting throughout
> (whatever that is).
> It looks like the original xsl file only used PMC, however a fairly
> early revision started using pmc and continued using PMC.
> Perhaps there was always an issue with some of the reports?
> 
> Until the correct setting is established, there's no point asking
> projects to fix their RDF files.
> 
> I don't know if there is a formal description of the syntax anywhere.
> 
> On 14 April 2015 at 00:00, Hervé BOUTEMY  wrote:
> > ok, it seems I can update the source, then I did it
> > 
> > I suppose this will be published in the next site content generation...
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le dimanche 12 avril 2015 04:41:22 Hervé BOUTEMY a écrit :
> >> Hi,
> >> 
> >> I'm working on http://projects-new.apache.org/ , which makes me dig into
> >> ASF DOAP conventions
> >> 
> >> And I found something that I think is a bug: on
> >> http://projects.apache.org/docs/pmc.html , half of the page explains
> >> about
> >> asfext:PMC in uppercase, while the other half is about asfext:pmc in
> >> lowercase
> >> 
> >> AFAIK, everybody is using asfext:pmc, in lowercase
> >> 
> >> Can you confirm that it is in lowercase? Then fix the page, that is
> >> causing
> >> a little bit of confusion?
> >> 
> >> Thanks in advance,
> >> 
> >> Hervé

Re: disabling edit feature in https://projects-new.apache.org/

[Hervé BOUTEMY]

while working on missing Forrest info, I'm now completely convinced we should 
not edit json but completely generate them from existing DOAP and project.a.o 
contents

then I'll immediately disable the edit feature: this can easily be reverted 
later

And I'll add a link to existing information on how to add a new TLP

Regards,

Hervé

Le dimanche 12 avril 2015 18:39:57 Hervé BOUTEMY a écrit :
> Hi,
> 
> I'm working on https://projects-new.apache.org/ , trying to figure out the
> whole information flow for informations about our projects: I like this new
> site, but IMHO we can't switch until we're clear on that.
> 
> 
> And it seems the edit feature currently cause inconsistencies since it edits
> site's svn simplified json content, instead of DOAP which is AFAIK the
> current project description standard [1]
> 
> 
> There are only few projects that used the feature, then it's not too late to
> fix the issue before it gets worse and people are lost.
> 
> 
> IMHO, adding a link to this DOAP page in projects-new's about page would do
> the job = explain people how to add their project (perhaps some additionnal
> instructions are required, I'm not sure)
> 
> WDYT?
> 
> Regards,
> 
> Hervé
> 
> [1] http://projects.apache.org/doap.html

Re: DOAP format question

[Hervé BOUTEMY]

ok, it seems I can update the source, then I did it

I suppose this will be published in the next site content generation...

Regards,

Hervé

Le dimanche 12 avril 2015 04:41:22 Hervé BOUTEMY a écrit :
> Hi,
> 
> I'm working on http://projects-new.apache.org/ , which makes me dig into ASF
> DOAP conventions
> 
> And I found something that I think is a bug: on
> http://projects.apache.org/docs/pmc.html , half of the page explains about
> asfext:PMC in uppercase, while the other half is about asfext:pmc in
> lowercase
> 
> AFAIK, everybody is using asfext:pmc, in lowercase
> 
> Can you confirm that it is in lowercase? Then fix the page, that is causing
> a little bit of confusion?
> 
> Thanks in advance,
> 
> Hervé

Re: projects-new.apache.org

[Hervé BOUTEMY]

ok, I added forrest to projects.json and it is now visible in projects list
https://projects-new.apache.org/projects.html

notice there may be issues with browser cache: json content doesn't seem to be 
refreshed when reloading page, I had to directly browse the json file and 
reload it
in the future, we may eed to do something to improve such refresh for end-
users who won't be able to do such tricks

Regards,

Hervé

Le lundi 13 avril 2015 08:09:40 Hervé BOUTEMY a écrit :
> great: I generated the json file [1]
> 
> now you are live!
> https://projects-new.apache.org/project.html?forrest
> 
> you still don't appear in the projects list: I need to investigate, will do
> tonight (Paris time).
> 
> Regards,
> 
> Hervé
> 
> [1] https://projects-new.apache.org/json/projects/forrest.json
> 
> Le lundi 13 avril 2015 14:41:07 David Crossley a écrit :
> > Hervé BOUTEMY wrote:
> > > I had a look at Forrest doap file[1]: it's not a doap file, it's a feed
> > > containing a doap entry
> > > 
> > > you should IMHO simplify it to match a simple doap file, like [2], for
> > > example
> > 
> > Ah, many thanks. I have now published that, and also updated the
> > reference in files.xml at the old projects.apache.org
> > http://svn.apache.org/r1673100
> > 
> > -David
> > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > [1] http://forrest.apache.org/doap.xml
> > > 
> > > [2]
> > > http://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf
> > > 
> > > Le lundi 13 avril 2015 04:58:05 Hervé BOUTEMY a écrit :
> > > > if you run parserdf.py, you'll see that forrest is one of the few rdf
> > > > that
> > > > makes the script choke:
> > > > 
> > > > Error when reading None's doap file
> > > > http://forrest.apache.org/doap.xml:
> > > > 
> > > > 
> > > > Traceback (most recent call last):
> > > >   File "rdfparse.py", line 59, in 
> > > >   
> > > > if pjson['homepage']:
> > > > KeyError: 'homepage'
> > > > 
> > > > 
> > > > 
> > > > I still didn't have time to investigate this one, and report (did it
> > > > for
> > > > lucy and uima: opened Jira issues on each project)
> > > > 
> > > > Regards,
> > > > 
> > > > Hervé
> > > > 
> > > > Le lundi 13 avril 2015 12:32:49 David Crossley a écrit :
> > > > > Apache Forrest is also missing from projects-new.a.o
> > > > > but was one of the early adopters at projects.a.o
> > > > > 
> > > > > I cannot determine why. Would someone else please try.
> > > > > 
> > > > > -David
> > > > > 
> > > > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote:
> > > > > > I finally found time to investigate:
> > > > > > 
> > > > > > this is because ofbiz is not in pmcs reference list [1] used by
> > > > > > the
> > > > > > site
> > > > > > to
> > > > > > create pmcs.json [2]
> > > > > > 
> > > > > > it seems one step was missed during OFBiz TLP creation [3]
> > > > > > 
> > > > > > As PMC Chair and/or member, you should be able to fix it [4]
> > > > > > 
> > > > > > Once done, just tell and I'll regenerate the pmcs.json file
> > > > > > 
> > > > > > Regards,
> > > > > > 
> > > > > > Hervé
> > > > > > 
> > > > > > 
> > > > > > [1]
> > > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/p
> > > > > > ro
> > > > > > ject
> > > > > > s
> > > > > > /data_files/
> > > > > > 
> > > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json
> > > > > > 
> > > > > > [3]
> > > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/p
> > > > > > ro
> > > > > > ject
> > > > > > s
> > > > > > /data_files/aareadme.txt
> > > > > > 
> > > > > > [4] http://projects.apache.org/create.html#submit
> > > > > > 
> > > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit :
> > > > > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by
> > > > > > > PMC'
> > > > > > > overview.
> > > > > > > 
> > > > > > > Best regards,
> > > > > > > 
> > > > > > > Pierre Smits

Re: projects-new.apache.org

[Hervé BOUTEMY]

great: I generated the json file [1]

now you are live!
https://projects-new.apache.org/project.html?forrest

you still don't appear in the projects list: I need to investigate, will do 
tonight (Paris time).

Regards,

Hervé

[1] https://projects-new.apache.org/json/projects/forrest.json

Le lundi 13 avril 2015 14:41:07 David Crossley a écrit :
> Hervé BOUTEMY wrote:
> > I had a look at Forrest doap file[1]: it's not a doap file, it's a feed
> > containing a doap entry
> > 
> > you should IMHO simplify it to match a simple doap file, like [2], for
> > example
> Ah, many thanks. I have now published that, and also updated the
> reference in files.xml at the old projects.apache.org
> http://svn.apache.org/r1673100
> 
> -David
> 
> > Regards,
> > 
> > Hervé
> > 
> > [1] http://forrest.apache.org/doap.xml
> > 
> > [2] http://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf
> > 
> > Le lundi 13 avril 2015 04:58:05 Hervé BOUTEMY a écrit :
> > > if you run parserdf.py, you'll see that forrest is one of the few rdf
> > > that
> > > makes the script choke:
> > > 
> > > Error when reading None's doap file http://forrest.apache.org/doap.xml:
> > > 
> > > 
> > > Traceback (most recent call last):
> > >   File "rdfparse.py", line 59, in 
> > >   
> > > if pjson['homepage']:
> > > KeyError: 'homepage'
> > > 
> > > 
> > > 
> > > I still didn't have time to investigate this one, and report (did it for
> > > lucy and uima: opened Jira issues on each project)
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > Le lundi 13 avril 2015 12:32:49 David Crossley a écrit :
> > > > Apache Forrest is also missing from projects-new.a.o
> > > > but was one of the early adopters at projects.a.o
> > > > 
> > > > I cannot determine why. Would someone else please try.
> > > > 
> > > > -David
> > > > 
> > > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote:
> > > > > I finally found time to investigate:
> > > > > 
> > > > > this is because ofbiz is not in pmcs reference list [1] used by the
> > > > > site
> > > > > to
> > > > > create pmcs.json [2]
> > > > > 
> > > > > it seems one step was missed during OFBiz TLP creation [3]
> > > > > 
> > > > > As PMC Chair and/or member, you should be able to fix it [4]
> > > > > 
> > > > > Once done, just tell and I'll regenerate the pmcs.json file
> > > > > 
> > > > > Regards,
> > > > > 
> > > > > Hervé
> > > > > 
> > > > > 
> > > > > [1]
> > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/pro
> > > > > ject
> > > > > s
> > > > > /data_files/
> > > > > 
> > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json
> > > > > 
> > > > > [3]
> > > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/pro
> > > > > ject
> > > > > s
> > > > > /data_files/aareadme.txt
> > > > > 
> > > > > [4] http://projects.apache.org/create.html#submit
> > > > > 
> > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit :
> > > > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC'
> > > > > > overview.
> > > > > > 
> > > > > > Best regards,
> > > > > > 
> > > > > > Pierre Smits