Re: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode!
Nope, not at all. On May 14, 2015, at 4:25 PM, Melissa Warnkin missywarn...@yahoo.com wrote: Good question. Or did you get anything from their booth that required them to scan your badge? From: Jim Jagielski j...@jagunet.com To: dev@community.apache.org Cc: operati...@apache.org operati...@apache.org Sent: Thursday, May 14, 2015 3:41 PM Subject: Fwd: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode! Hrm Is this SPAM due to Pivotal getting my Email via the ACUS roster? Disappointed. Begin forwarded message: From: Andrea Rojas anro...@pivotal.io Subject: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode! Date: May 14, 2015 at 10:51:16 AM EDT To: j...@apache.org Reply-To: anro...@pivotal.io Message-Id: 1063550227.890044935.1431615076532.javamail.r...@sjmas02.marketo.org http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC Hi Jim, Pivotal had a lot going on this year as a Platinum sponsor at ApacheCon. In addition to several excellent sessions, Pivotal also debuted Apache Geode http://info.pivotal.io/eA0FxJ02010UIR0kWa0Na0C (now incubating) – the new in-memory distributed database that will form the open source core of Pivotal GemFire http://info.pivotal.io/HI0020k0Aa1FRJW1NaU00yC. Pivotal is looking for supporters for the Apache Geode technology and community. Check out this blog http://info.pivotal.io/FaFUN00z20I1a2Rk000JCAW for information on how to get involved. For additional opportunities to support the effort: Visit the Apache Geode page http://info.pivotal.io/DIAW0030JUF00R1aNA2a0Ck Participate in the Apache Geode community http://info.pivotal.io/E0C0I1a4UBF0A0kJ2R0WN0a Learn how you can become a project contributor to this powerful in-memory, distributed database in this video http://info.pivotal.io/CUa0050CN1RI0ACF2k0aJ0W Join this webinar http://info.pivotal.io/GaU0JR20F6WDI0CN0100aAk on June 2nd for a technical tutorial demonstrating how to use in-memory data grid technologies and add these capabilities to your applications Want more? Come see Pivotal in action at a Pivotal Big Data Roadshow http://info.pivotal.io/x0IR2Ea1NAU07CWaFJk or Pivotal Cloud Platform Roadshow http://info.pivotal.io/Ba008I2JA000W1RU0FFNakC near you. We look forward to seeing you at our next event http://info.pivotal.io/i9RI0AUaaGN00C010Fk2J0W! Sincerely, The Pivotal Team pivotal.io http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC http://info.pivotal.io/kI1aN0A00Ra02UCkFa0HW0J http://info.pivotal.io/NU00IIkC001aaRJ0bAW0F2N http://info.pivotal.io/ZUAWa0acC0001k0FJ20NJIR http://info.pivotal.io/Y0CWR0dAa00kF012NUI0KJa http://info.pivotal.io/TeAIR0a0a000FUL21NWkCJ0 Pivotal http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC is a trusted partner for IT innovation, enabling enterprises to provide modern software-driven experiences for their customers and workforces. The combination of leading agile development services, an open cloud platform and open suite of big data products accelerate innovation cycles for our customers across every industry. More at pivotal.io. http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC © Pivotal, and the Pivotal logo are registered trademarks or trademarks of Pivotal Software, Inc. in the United States and other countries. All other trademarks used herein are the property of their respective owners. © 2015 Pivotal Software, Inc. All rights reserved. Published in the USA. Unsubscribe http://info.pivotal.io/a0201N0akI0F00fJMUARWaC
Re: projects-new.a.o updates
On 05/14/2015 06:38 PM, Hervé BOUTEMY wrote: Feedback expected:) You rock. -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
Re: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode!
Roman, Thank you for checking into this. Have a great day! ~M From: Roman Shaposhnik ro...@shaposhnik.org To: ComDev dev@community.apache.org Sent: Thursday, May 14, 2015 7:10 PM Subject: Re: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode! Turns out it was an over-eager corp. marketing that used sources unrelated to ACNA to figure out who may be interested in Geode (whatever that means). Apologies for the noise, my initial thought was exactly along the lines of Melissa's note: whoever got scanned (which in my mind would be a totally fair game). I now confirmed it wasn't that. Once again -- apologies. I tried to make it as clear as possible that this is NOT cool. I really hope it doesn't happen again (although we will scan your badges if you want our swag ;-)). Thanks, Roman. On Thu, May 14, 2015 at 3:58 PM, jan i j...@apache.org wrote: Just to balance the ladder a little bit. Even though I am mentor for the newest Pivotal kid in town, I did not receive the mail. I know that LF has a very strict policy. rgds jan I On Friday, May 15, 2015, Shane Curcuru a...@shanecurcuru.org wrote: On 5/14/15 3:41 PM, Jim Jagielski wrote: Hrm Is this SPAM due to Pivotal getting my Email via the ACUS roster? My understanding of LF event policy (who runs the reg and conference for us) is that they do *not* share email lists with vendors. I got the below email also, to my @apache.org email address, which I do not use for LF registration, so they clearly got it some other way. - Shane Disappointed. Begin forwarded message: *From: *Andrea Rojas anro...@pivotal.io javascript:; mailto: anro...@pivotal.io javascript:; *Subject: **Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode!* *Date: *May 14, 2015 at 10:51:16 AM EDT *To: *j...@apache.org javascript:; mailto:j...@apache.org javascript:; *Reply-To: *anro...@pivotal.io javascript:; mailto: anro...@pivotal.io javascript:; *Message-Id: *1063550227.890044935.1431615076532.javamail.r...@sjmas02.marketo.org javascript:; mailto: 1063550227.890044935.1431615076532.javamail.r...@sjmas02.marketo.org javascript:; http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC Hi Jim, Pivotal had a lot going on this year as a Platinum sponsor at ApacheCon. In addition to several excellent sessions, Pivotal also debuted Apache Geode http://info.pivotal.io/eA0FxJ02010UIR0kWa0Na0C (now incubating) – the new in-memory distributed database that will form the open source core of Pivotal GemFire http://info.pivotal.io/HI0020k0Aa1FRJW1NaU00yC . Pivotal is looking for supporters for the Apache Geode technology and community. Check out this blog http://info.pivotal.io/FaFUN00z20I1a2Rk000JCAW for information on how to get involved. For additional opportunities to support the effort: * Visit the Apache Geode page http://info.pivotal.io/DIAW0030JUF00R1aNA2a0Ck * Participate in the Apache Geode community http://info.pivotal.io/E0C0I1a4UBF0A0kJ2R0WN0a * Learn how you can become a project contributor to this powerful in-memory, distributed database in this video http://info.pivotal.io/CUa0050CN1RI0ACF2k0aJ0W * Join this webinar http://info.pivotal.io/GaU0JR20F6WDI0CN0100aAk on June 2nd for a technical tutorial demonstrating how to use in-memory data grid technologies and add these capabilities to your applications Want more? Come see Pivotal in action at a Pivotal Big Data Roadshow http://info.pivotal.io/x0IR2Ea1NAU07CWaFJk or Pivotal Cloud Platform Roadshow http://info.pivotal.io/Ba008I2JA000W1RU0FFNakC near you. We look forward to seeing you at our next event http://info.pivotal.io/i9RI0AUaaGN00C010Fk2J0W! Sincerely, The Pivotal Team pivotal.io http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC Follow us on Twitter http://info.pivotal.io/kI1aN0A00Ra02UCkFa0HW0J Join the conversation on LinkedIn http://info.pivotal.io/NU00IIkC001aaRJ0bAW0F2N Like us on Facebook http://info.pivotal.io/ZUAWa0acC0001k0FJ20NJIR Add us on Google+ http://info.pivotal.io/Y0CWR0dAa00kF012NUI0KJa Visit our YouTube channel http://info.pivotal.io/TeAIR0a0a000FUL21NWkCJ0 Pivotal http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC is a trusted partner for IT innovation, enabling enterprises to provide modern software-driven experiences for their customers and workforces. The combination of leading agile development services, an open cloud platform and open suite of big data products accelerate innovation cycles for our customers across every industry. More at pivotal.io. http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC © Pivotal, and the Pivotal logo are registered trademarks or trademarks of Pivotal Software, Inc. in the United States and other countries. All other trademarks used herein are the property of their respective owners. © 2015 Pivotal Software, Inc. All rights
Re: projects-new.a.o updates
On 14 May 2015 at 23:38, Hervé BOUTEMY herve.bout...@free.fr 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. It would be better to use distinct namespaces for distinct types of item. 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? Where do they originate? 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
On 15 May 2015 at 22:08, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le vendredi 15 mai 2015 14:02:52 sebb a écrit :
On 14 May 2015 at 23:38, Hervé BOUTEMY herve.bout...@free.fr 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.
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; a project is a software artifact.
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/
答复: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode!
-原始邮件- 发件人: Jim Jagielski j...@jagunet.com 发送时间: 5/15/2015 8:01 PM 收件人: operati...@apache.org operati...@apache.org; Melissa Warnkin missywarn...@yahoo.com 抄送: dev@community.apache.org dev@community.apache.org 主题: Re: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode! Nope, not at all. On May 14, 2015, at 4:25 PM, Melissa Warnkin missywarn...@yahoo.com wrote: Good question. Or did you get anything from their booth that required them to scan your badge? From: Jim Jagielski j...@jagunet.com To: dev@community.apache.org Cc: operati...@apache.org operati...@apache.org Sent: Thursday, May 14, 2015 3:41 PM Subject: Fwd: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode! Hrm Is this SPAM due to Pivotal getting my Email via the ACUS roster? Disappointed. Begin forwarded message: From: Andrea Rojas anro...@pivotal.io Subject: Thank You for Joining Pivotal at ApacheCon and Welcome Apache Geode! Date: May 14, 2015 at 10:51:16 AM EDT To: j...@apache.org Reply-To: anro...@pivotal.io Message-Id: 1063550227.890044935.1431615076532.javamail.r...@sjmas02.marketo.org http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC Hi Jim, Pivotal had a lot going on this year as a Platinum sponsor at ApacheCon. In addition to several excellent sessions, Pivotal also debuted Apache Geode http://info.pivotal.io/eA0FxJ02010UIR0kWa0Na0C (now incubating) – the new in-memory distributed database that will form the open source core of Pivotal GemFire http://info.pivotal.io/HI0020k0Aa1FRJW1NaU00yC. Pivotal is looking for supporters for the Apache Geode technology and community. Check out this blog http://info.pivotal.io/FaFUN00z20I1a2Rk000JCAW for information on how to get involved. For additional opportunities to support the effort: Visit the Apache Geode page http://info.pivotal.io/DIAW0030JUF00R1aNA2a0Ck Participate in the Apache Geode community http://info.pivotal.io/E0C0I1a4UBF0A0kJ2R0WN0a Learn how you can become a project contributor to this powerful in-memory, distributed database in this video http://info.pivotal.io/CUa0050CN1RI0ACF2k0aJ0W Join this webinar http://info.pivotal.io/GaU0JR20F6WDI0CN0100aAk on June 2nd for a technical tutorial demonstrating how to use in-memory data grid technologies and add these capabilities to your applications Want more? Come see Pivotal in action at a Pivotal Big Data Roadshow http://info.pivotal.io/x0IR2Ea1NAU07CWaFJk or Pivotal Cloud Platform Roadshow http://info.pivotal.io/Ba008I2JA000W1RU0FFNakC near you. We look forward to seeing you at our next event http://info.pivotal.io/i9RI0AUaaGN00C010Fk2J0W! Sincerely, The Pivotal Team pivotal.io http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC http://info.pivotal.io/kI1aN0A00Ra02UCkFa0HW0J http://info.pivotal.io/NU00IIkC001aaRJ0bAW0F2N http://info.pivotal.io/ZUAWa0acC0001k0FJ20NJIR http://info.pivotal.io/Y0CWR0dAa00kF012NUI0KJa http://info.pivotal.io/TeAIR0a0a000FUL21NWkCJ0 Pivotal http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC is a trusted partner for IT innovation, enabling enterprises to provide modern software-driven experiences for their customers and workforces. The combination of leading agile development services, an open cloud platform and open suite of big data products accelerate innovation cycles for our customers across every industry. More at pivotal.io. http://info.pivotal.io/HI0020k0AaZFRJW1NaU00wC © Pivotal, and the Pivotal logo are registered trademarks or trademarks of Pivotal Software, Inc. in the United States and other countries. All other trademarks used herein are the property of their respective owners. © 2015 Pivotal Software, Inc. All rights reserved. Published in the USA. Unsubscribe http://info.pivotal.io/a0201N0akI0F00fJMUARWaC Q
Re: Project Visualization Tool...
On 16 May 2015 at 00:30, sebb seb...@gmail.com wrote: On 15 May 2015 at 23:28, Hervé BOUTEMY herve.bout...@free.fr 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 asfext:pmd rdf:resource=URL/ where URL is either an actual URL of a PMC data file or a dummy URL e.g. asfext:pmc rdf:resource=http://pmcname.apache.org / which leads to a file here: https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/da ta_files/pmcname.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. 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. But other information manually written in current PMC data rdf files can't be found anywhere else, AFAIK. Yes. 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 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, its 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: That does not seem necessary. 3. Sub-projects (8): to Projects (8):, eventually boldening the TLP if one is the TLP No - none of the projects are the TLP. The TLP / PMC is not the same as any of its projects. Most PMCs happen to have the same name as one of their projects, but they are distinct entities. Note that the Creadur PMC does not have a Creadur project. To take the Ant example, there needs to be an Ant PMC/TLP page and a separate Ant project page. These should be linked somehow. and I should rename tlps.json to committees.json (and update code accordingly) No need. then on https://projects-new.apache.org/ , do we really want to graph TLPs evolution or committees? No idea I suppose commons can be called a TLP, even if it does not have any main project that is the effective TLP Yes, Commons is a TLP/PMC. I don't think it's helpful to think of PMCs having a main project. PMCs have one or more projects; each project has a single PMC. comdev is not really a TLP: should probably not be listed in projects list, but as special committee not producing projects? Well, it is responsible for this mailing list and is probably responsible for the projects.a.o website. is Labs a TLP? or like comdev? What does committee-info.txt say? 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
Re: Project Visualization Tool...
On 5 May 2015 at 07:38, Hervé BOUTEMY herve.bout...@free.fr wrote: 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 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. 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 asfext:pmd rdf:resource=URL/ where URL is either an actual URL of a PMC data file or a dummy URL e.g. asfext:pmc rdf:resource=http://pmcname.apache.org / which leads to a file here: https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/pmcname.rdf 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, its 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. 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
Re: I'm looking for State of the Feather filetype:pptx
My typos! Thanks On Saturday, May 16, 2015, Andrea Pescetti pesce...@apache.org wrote: Edward J. Yoon wrote: Just FYI, here's my slides - https://docs.google.com/presentation/d/1ScAzW37oEYnaYR8yNZCyJlk_lnssSAXopeZ0NUmPoeg/edit?usp=sharing What do you mean by ASF philosophy is that code can be used commercially w/ restrictions? If it's not a typo, can you expand on it? The rest looks good to me! Regards, Andrea. -- Best Regards, Edward J. Yoon
Re: projects-new.a.o updates
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 herve.bout...@free.fr 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/
Re: projects-new.a.o updates
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: I'm looking for State of the Feather filetype:pptx
Edward J. Yoon wrote: Just FYI, here's my slides - https://docs.google.com/presentation/d/1ScAzW37oEYnaYR8yNZCyJlk_lnssSAXopeZ0NUmPoeg/edit?usp=sharing What do you mean by ASF philosophy is that code can be used commercially w/ restrictions? If it's not a typo, can you expand on it? The rest looks good to me! Regards, Andrea.
Re: projects-new.a.o updates
Le vendredi 15 mai 2015 14:02:52 sebb a écrit :
On 14 May 2015 at 23:38, Hervé BOUTEMY herve.bout...@free.fr 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/
