help reviewing ApacheCon proposals

[Jan Willem Janssen]

Hi,

I would like to help out reviewing the proposals of the upcoming
ApacheCon. I already did this in the past, but it appears my
review-karma has been revoked. What do I need to do to regain
this?

--
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814


My world is something with Amdatu and Apache

Luminis Technologies
Churchillplein 1
7314 BZ  Apeldoorn
+31 88 586 46 00

https://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8170.94.441.B.01



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: I want to subscribe to mailing lists

[Matthias J. Sax]

https://spark.apache.org/community.html

On 02/11/2016 08:34 PM, Shyam Sarkar wrote:
> u...@spark.apache.org
> 
> d...@spark.apache.org
> 



signature.asc
Description: OpenPGP digital signature

Re: I want to subscribe to mailing lists

[Shyam Sarkar]

Do I have @apache.org e-mail address ?  I am getting following error when\
I send from ssarkarayushnet...@gmail.com address:

mailer-dae...@apache.org

to me
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
Must be sent from an @apache.org address or a subscriber address or an
address in LDAP.

Thanks.

On Thu, Feb 11, 2016 at 11:35 AM, Matthias J. Sax  wrote:

> https://spark.apache.org/community.html
>
> On 02/11/2016 08:34 PM, Shyam Sarkar wrote:
> > u...@spark.apache.org
> >
> > d...@spark.apache.org
> >
>
>

I want to subscribe to mailing lists

[Shyam Sarkar]

u...@spark.apache.org

d...@spark.apache.org

Re: Adding asfext:registered to projects.a.o?

[Stian Soiland-Reyes]

How about something very modern - moving to JSON-LD schema.org annotations
in the root index of the project homepage and just fetching all of those..?

Seriously; keeping them under a single comdev control sounds most sensible
as I doubt the distributed DOAP files are well maintained.  Projects can
raise pull requests to update and then see their changes live on the new
projects.apache.org pages
On 11 Feb 2016 17:35, "sebb"  wrote:

> On 11 February 2016 at 12:03, Shane Curcuru  wrote:
> > I need to annotate our structured data set of Apache projects to track
> > which project names are registered trademarks.  This is needed to be
> > able to properly generate a.o/foundation/marks/list (which is currently
> > sadly outdated since it's manually built now).  This is a serious need
> > for Brand Management, since we regularly have third parties say "but you
> > didn't SAY it was your trademark, so I can do it anyway..."
> >
> > My thought is to annotate the PMC DOAP files with a registered marker,
> > then use the existing projects.a.o building of the organized data.  Then
> > use either JS or some cron static generation to display the actual
> > marks/list page.
>
> There are two kinds of RDF files:
> - the PMC RDF files [1] which are mainly stored in the comdev area
> [2], though they can also be stored elsewhere.
> The locations of the files are held in committees.xml [3]
> [These are not actually DOAP files, though the format looks similar.]
>
> - the project DOAP files which are stored by individual projects; they
> are listed in projects.xml [4]
>
> A single PMC RDF file can be associated with multiple DOAP files, e.g.
> Commons, Creadur, Tomcat all have multiple independent project
> releases.
>
> > Is annotating the project data sources the best idea, or should I simply
> > create a new stable URL data source that's just a list of registered
> > names, and join the tables?
>
> I doubt if either of the above file types are suitable.
> The location of the index XML files [3], [4] has already been changed
> once (when projects-new was established).
>
> DOAP files are located all over the place and are often moved within
> the SCM without updating the index file.
> If they are located in the source tree there are often multiple copies
> in different branches.
>
> PMC RDF files may not be updateable except by the project (if located
> in their SCM), and again may move without warning if they are not in
> [2].
>
> It would potentially be possible to recover the PMC RDF files from
> their external locations and insist that they only be stored in the
> comdev area.
> But a single PMC may have multiple marks. Potentially also a project
> may move from a PMC to become its own PMC.
>
> Therefore I think a separate file is needed.
> That would also allow write access to be limited if necessary.
>
> > The end result needs to be webcontent listing projects like:
> >
> > The ASF claims these trademarks
> > ...list all active TLPs
> > Apache {$projectname}
> > {$if registered then "" else ""}
> >
> > 
> >   {$shortdesc}
> > ...
> > The following projects are retired
> > ...list all Attic projects
> >
> > The following projects are in incubation; all trademarks here may be
> > property of respective owners
> > ...list all Incubation projects
> >
> > Separately, we should list the name of each software *product* here,
> > since if we offer something with a clear name as an independently
> > downloadable software product, it can be our trademark.  So I'd like to
> > list "Apache Directory Studio", since that's a notable name and a major
> > product.  But I don't want to list "Apache Commons Foo Bar Baz and
> > Kitchensink", since those are effectively just minor components that
> > aren't really worth claiming.
> >
> > Comments/suggestions please?  I'm including the Whimsical project since
> > they are also major consumers of this data.
> >
> > - Shane
>
> [1] https://projects.apache.org/pmc_rdf.html
>
> [2]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees/
> [3]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml
> [4]
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml
>

Re: Adding asfext:registered to projects.a.o?

[Sam Ruby]

On Thu, Feb 11, 2016 at 2:38 PM, Stian Soiland-Reyes  wrote:
> How about something very modern - moving to JSON-LD schema.org annotations
> in the root index of the project homepage and just fetching all of those..?
>
> Seriously; keeping them under a single comdev control sounds most sensible
> as I doubt the distributed DOAP files are well maintained.  Projects can
> raise pull requests to update and then see their changes live on the new
> projects.apache.org pages

I agree with centralize first, and decentralize when the need shows itself.

As for format: let prototype.  Seriously.

If Shane can provide some initial test data in any format (e.g. CSV) I
can convert that to YAML and you can convert it to JSON-LD, and Shane
can determine which would be easier for him to maintain.  I'll also go
the extra step and write a small script that converts it to JSON
(note: POJO, not LD), and write an ugly page that fetches and displays
that data.  Others can do likewise.

Shane should be able to use these programs as examples and extend them
as he sees fit.

- Sam Ruby

> On 11 Feb 2016 17:35, "sebb"  wrote:
>
>> On 11 February 2016 at 12:03, Shane Curcuru  wrote:
>> > I need to annotate our structured data set of Apache projects to track
>> > which project names are registered trademarks.  This is needed to be
>> > able to properly generate a.o/foundation/marks/list (which is currently
>> > sadly outdated since it's manually built now).  This is a serious need
>> > for Brand Management, since we regularly have third parties say "but you
>> > didn't SAY it was your trademark, so I can do it anyway..."
>> >
>> > My thought is to annotate the PMC DOAP files with a registered marker,
>> > then use the existing projects.a.o building of the organized data.  Then
>> > use either JS or some cron static generation to display the actual
>> > marks/list page.
>>
>> There are two kinds of RDF files:
>> - the PMC RDF files [1] which are mainly stored in the comdev area
>> [2], though they can also be stored elsewhere.
>> The locations of the files are held in committees.xml [3]
>> [These are not actually DOAP files, though the format looks similar.]
>>
>> - the project DOAP files which are stored by individual projects; they
>> are listed in projects.xml [4]
>>
>> A single PMC RDF file can be associated with multiple DOAP files, e.g.
>> Commons, Creadur, Tomcat all have multiple independent project
>> releases.
>>
>> > Is annotating the project data sources the best idea, or should I simply
>> > create a new stable URL data source that's just a list of registered
>> > names, and join the tables?
>>
>> I doubt if either of the above file types are suitable.
>> The location of the index XML files [3], [4] has already been changed
>> once (when projects-new was established).
>>
>> DOAP files are located all over the place and are often moved within
>> the SCM without updating the index file.
>> If they are located in the source tree there are often multiple copies
>> in different branches.
>>
>> PMC RDF files may not be updateable except by the project (if located
>> in their SCM), and again may move without warning if they are not in
>> [2].
>>
>> It would potentially be possible to recover the PMC RDF files from
>> their external locations and insist that they only be stored in the
>> comdev area.
>> But a single PMC may have multiple marks. Potentially also a project
>> may move from a PMC to become its own PMC.
>>
>> Therefore I think a separate file is needed.
>> That would also allow write access to be limited if necessary.
>>
>> > The end result needs to be webcontent listing projects like:
>> >
>> > The ASF claims these trademarks
>> > ...list all active TLPs
>> > Apache {$projectname}
>> > {$if registered then "" else ""}
>> >
>> > 
>> >   {$shortdesc}
>> > ...
>> > The following projects are retired
>> > ...list all Attic projects
>> >
>> > The following projects are in incubation; all trademarks here may be
>> > property of respective owners
>> > ...list all Incubation projects
>> >
>> > Separately, we should list the name of each software *product* here,
>> > since if we offer something with a clear name as an independently
>> > downloadable software product, it can be our trademark.  So I'd like to
>> > list "Apache Directory Studio", since that's a notable name and a major
>> > product.  But I don't want to list "Apache Commons Foo Bar Baz and
>> > Kitchensink", since those are effectively just minor components that
>> > aren't really worth claiming.
>> >
>> > Comments/suggestions please?  I'm including the Whimsical project since
>> > they are also major consumers of this data.
>> >
>> > - Shane
>>
>> [1] https://projects.apache.org/pmc_rdf.html
>>
>> [2]
>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees/
>> [3]
>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml
>> [4]
>> 

RE: ASF GSoC mentor eligibility

[Ross Gardler]

Mentoring an ASF project, formally, requires you to have an ASF commit bit on 
the project you are mentoring for. However, the act of mentoring is a community 
effort. Engage with your project community offering your assistance and asking 
for someone to work with you as the named mentor. If you can find such a person 
then you are good to go.

Ross

-Original Message-
From: Melissa Warnkin [mailto:missywarn...@yahoo.com.INVALID] 
Sent: Thursday, February 11, 2016 12:48 PM
To: dev@community.apache.org
Subject: Re: ASF GSoC mentor eligibility

Hi Paulo,
Thank you for your interest in becoming a GSoC mentor.  Someone will get back 
to you shortly with the answers to your questions.
Have a great day,
~MelissaExecutive AssistantASF

  From: Paulo Motta 
 To: dev@community.apache.org
 Sent: Wednesday, February 10, 2016 5:01 PM
 Subject: ASF GSoC mentor eligibility
   
Hello,

I'm a community member and active contributor of an Apache project and I'd like 
to volunteer to be a GSoC mentor this year. However, I'm not currently an ASF 
committer or member.

I'd like to clarify if GSoC mentoring is strictly restricted to ASF committers 
or can non-committers also volunteer to be mentors or co-mentors?

ps: I'm sending to this list as I didn't find a clear answer on 
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fcommunity.apache.org%2fguide-to-being-a-mentor.html.=01%7c01%7cRoss.Gardler%40microsoft.com%7c02cbb89e2f8f4a3adf0808d333249a9d%7c72f988bf86f141af91ab2d7cd011db47%7c1=5U6Twfl3%2bCz%2fzqXx0ldsCLx%2fxXT%2fkvjGO7Q%2bvoW0qJo%3d

Thanks,

Paulo


  

Re: I want to subscribe to mailing lists

[Josh Elser]

No, you need to send to the subscribe address as that community page 
instructs:


mailto:user-subscr...@spark.apache.org

and

mailto:dev-subscr...@spark.apache.org

Shyam Sarkar wrote:

Do I have @apache.org e-mail address ?  I am getting following error when\
I send from ssarkarayushnet...@gmail.com address:

mailer-dae...@apache.org

to me
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
Must be sent from an @apache.org address or a subscriber address or an
address in LDAP.

Thanks.

On Thu, Feb 11, 2016 at 11:35 AM, Matthias J. Sax  wrote:


https://spark.apache.org/community.html

On 02/11/2016 08:34 PM, Shyam Sarkar wrote:

u...@spark.apache.org

d...@spark.apache.org

Re: ASF GSoC mentor eligibility

[Melissa Warnkin]

Hi Paulo,
Thank you for your interest in becoming a GSoC mentor.  Someone will get back 
to you shortly with the answers to your questions.
Have a great day,
~MelissaExecutive AssistantASF

  From: Paulo Motta 
 To: dev@community.apache.org 
 Sent: Wednesday, February 10, 2016 5:01 PM
 Subject: ASF GSoC mentor eligibility
   
Hello,

I'm a community member and active contributor of an Apache project and I'd
like to volunteer to be a GSoC mentor this year. However, I'm not currently
an ASF committer or member.

I'd like to clarify if GSoC mentoring is strictly restricted to ASF
committers or can non-committers also volunteer to be mentors or co-mentors?

ps: I'm sending to this list as I didn't find a clear answer on
https://community.apache.org/guide-to-being-a-mentor.html.

Thanks,

Paulo


  

Re: Help Wanted! (it's a title, not a request!)

[Melissa Warnkin]

Hi Roman,
Thank you for participating in hackillinois and facilitating student 
contributions to the ASF projects! Super cool!!
Sooo...I got to thinking (I knooow...that's always dangerous!!), while you're 
there please spread the word about ApacheCon and TAC; we're trying to encourage 
more students to apply for TAC, so this is a perfect opportunity!! Although it 
won't be beneficial for this ApacheCon, it would still be helpful to spread the 
word!
Detailed information on the Travel Assistance can be found here:  
http://apache.org/travel/
Details on how to apply for travel assistance can be found here:  
http://apache.org/travel/#applying.
The TAC would very much appreciate it if you could spread the word.
Thanks, Roman, and have a fantastic day!
~Melissaon behalf of the Travel Assistance Committee

  From: Roman Shaposhnik 
 To: ComDev  
 Sent: Wednesday, February 10, 2016 2:17 PM
 Subject: Re: Help Wanted! (it's a title, not a request!)
   
Hi!

I wanted to amplify Ross' concerns, but I wasn't sure how to cast
it in an actionable way. As the luck would have it -- now I do. So
here's what I'm struggling with: as many of you should know by
now there's a live event schedule for Feb 19-21:
    http://hackillinois.org/opensource
    https://hackillinois.org/

Think of it as Google Summer of Code, but done live and on a much
more compressed schedule. I got invited there to help facilitate student
contributions to the ASF projects. I have a wide exposure to at least
Big Data ASF ecosystem so I can guide them through the basics and
I can help with mechanics of contributing to ASF. That's all good.

The only thing I can NOT do all by myself is figure out how different
ASF communities would like to leverage this free labor (and hopefully
build lasting relationships with some of these students). My thought was
to do what we typically do for GSoC -- reach out to all these communities
and suggest that they either tell me how to get the list of 'low hanging fruit'
JIRAs/ideas or suggest they tag the ones they would like me to offer
to students with 'hackillinois2016' tag. Pretty easy hand off.

Now with the http://helpwanted.a.o/entering the picture how do you suggest
I frame this ask I was about to send out today?

Thanks,
Roman.

On Mon, Feb 8, 2016 at 11:31 AM, Daniel Gruno  wrote:
> On 02/08/2016 07:40 PM, Ross Gardler wrote:
>> This is great, but...
>>
>> The success of something like this is not in the tool, it's in the content.
>
> Very true - if nobody's using it, it doesn't matter if it exists or not.
>
>>
>> I worry that by requiring projects to enter the data separately to their 
>> chosen issue tracker we are reducing the chances of this succeeding (and it 
>> deserves to succeed as a tool). Furthermore, when it comes around to GSoC 
>> projects across the foundation already mark tasks as "mentor".
>
>
> The reasoning here was, that short of implementing 50 new components as
> obligatory components in every single JIRA (which would take oodles of
> time), we don't really have a way of uniformly conforming to a simple
> way of seeing which tasks are out there, and even then, getting the word
> out is tricky. Telling someone to "go look at JIRA" can be quite
> off-putting if you're not exactly an expert in navigating it.
> Furthermore, I'm not aware of any short'n'simple way of taking
> integrating that on the project web sites, short of putting a LOT of
> stress on JIRA (and thus slowing down all web sites).
>
> So we thought of a way to enable projects to all do this the same way,
> thereby making it possible for someone to find something across all
> projects, or for projects to implement it on their web sites regardless
> of what those are comprised of. The widget is something I'm very pleased
> with, as projects can choose to show what THEY want done, but also what
> any other project would like to see done, in a concise manner.
>
>>
>> I hear the concern that some projects use Bugzilla, but the majority use 
>> Jira.
>>
>> Can we do imports from Jira, filtered by the "mentor" label?
>
> It could, yes - we'd just write an import script for it. Possible add to
> it so it could auto-close issues as well. But it would require projects
> to write their mentoring tasks using a specific syntax, or it wouldn't
> be able to convert it to the simple format HW uses.
>
> If someone can come up with a syntax to use, I would be willing to write
> a parser for it that adds a HW task pointing to that JIRA.
>
> The way I see it, HW is only a primer, and JIRA/BZ or the ML is where
> the actual discussion would happen. This isn't going to turn into some
> big tool with user logins etc, I would keep this very very simple as an
> aggregator of multiple sources as well as keep the current option of
> manually entering something into the system.
>
> WDYT?
>
> With regards,
> Daniel.
>
>>
>> Ross
>>

  

Re: ASF GSoC mentor eligibility

[Abdo Lwafi]

Le 10 févr. 2016 22:02, "Paulo Motta"  a écrit :

> Hello,
>
> I'm a community member and active contributor of an Apache project and I'd
> like to volunteer to be a GSoC mentor this year. However, I'm not currently
> an ASF committer or member.
>
> I'd like to clarify if GSoC mentoring is strictly restricted to ASF
> committers or can non-committers also volunteer to be mentors or
> co-mentors?
>
> ps: I'm sending to this list as I didn't find a clear answer on
> https://community.apache.org/guide-to-being-a-mentor.html.
>
> Thanks,
>
> Paulo
>

Re: Adding asfext:registered to projects.a.o?

[sebb]

On 11 February 2016 at 12:03, Shane Curcuru  wrote:
> I need to annotate our structured data set of Apache projects to track
> which project names are registered trademarks.  This is needed to be
> able to properly generate a.o/foundation/marks/list (which is currently
> sadly outdated since it's manually built now).  This is a serious need
> for Brand Management, since we regularly have third parties say "but you
> didn't SAY it was your trademark, so I can do it anyway..."
>
> My thought is to annotate the PMC DOAP files with a registered marker,
> then use the existing projects.a.o building of the organized data.  Then
> use either JS or some cron static generation to display the actual
> marks/list page.

There are two kinds of RDF files:
- the PMC RDF files [1] which are mainly stored in the comdev area
[2], though they can also be stored elsewhere.
The locations of the files are held in committees.xml [3]
[These are not actually DOAP files, though the format looks similar.]

- the project DOAP files which are stored by individual projects; they
are listed in projects.xml [4]

A single PMC RDF file can be associated with multiple DOAP files, e.g.
Commons, Creadur, Tomcat all have multiple independent project
releases.

> Is annotating the project data sources the best idea, or should I simply
> create a new stable URL data source that's just a list of registered
> names, and join the tables?

I doubt if either of the above file types are suitable.
The location of the index XML files [3], [4] has already been changed
once (when projects-new was established).

DOAP files are located all over the place and are often moved within
the SCM without updating the index file.
If they are located in the source tree there are often multiple copies
in different branches.

PMC RDF files may not be updateable except by the project (if located
in their SCM), and again may move without warning if they are not in
[2].

It would potentially be possible to recover the PMC RDF files from
their external locations and insist that they only be stored in the
comdev area.
But a single PMC may have multiple marks. Potentially also a project
may move from a PMC to become its own PMC.

Therefore I think a separate file is needed.
That would also allow write access to be limited if necessary.

> The end result needs to be webcontent listing projects like:
>
> The ASF claims these trademarks
> ...list all active TLPs
> Apache {$projectname}
> {$if registered then "" else ""}
>
> 
>   {$shortdesc}
> ...
> The following projects are retired
> ...list all Attic projects
>
> The following projects are in incubation; all trademarks here may be
> property of respective owners
> ...list all Incubation projects
>
> Separately, we should list the name of each software *product* here,
> since if we offer something with a clear name as an independently
> downloadable software product, it can be our trademark.  So I'd like to
> list "Apache Directory Studio", since that's a notable name and a major
> product.  But I don't want to list "Apache Commons Foo Bar Baz and
> Kitchensink", since those are effectively just minor components that
> aren't really worth claiming.
>
> Comments/suggestions please?  I'm including the Whimsical project since
> they are also major consumers of this data.
>
> - Shane

[1] https://projects.apache.org/pmc_rdf.html

[2] https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees/
[3] 
https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml
[4] 
https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml

Re: Adding asfext:registered to projects.a.o?

[Sam Ruby]

On Thu, Feb 11, 2016 at 11:35 AM, sebb  wrote:
> On 11 February 2016 at 12:03, Shane Curcuru  wrote:
>> I need to annotate our structured data set of Apache projects to track
>> which project names are registered trademarks.  This is needed to be
>> able to properly generate a.o/foundation/marks/list (which is currently
>> sadly outdated since it's manually built now).  This is a serious need
>> for Brand Management, since we regularly have third parties say "but you
>> didn't SAY it was your trademark, so I can do it anyway..."
>>
>> My thought is to annotate the PMC DOAP files with a registered marker,
>> then use the existing projects.a.o building of the organized data.  Then
>> use either JS or some cron static generation to display the actual
>> marks/list page.
>
> There are two kinds of RDF files:
> - the PMC RDF files [1] which are mainly stored in the comdev area
> [2], though they can also be stored elsewhere.
> The locations of the files are held in committees.xml [3]
> [These are not actually DOAP files, though the format looks similar.]
>
> - the project DOAP files which are stored by individual projects; they
> are listed in projects.xml [4]
>
> A single PMC RDF file can be associated with multiple DOAP files, e.g.
> Commons, Creadur, Tomcat all have multiple independent project
> releases.
>
>> Is annotating the project data sources the best idea, or should I simply
>> create a new stable URL data source that's just a list of registered
>> names, and join the tables?
>
> I doubt if either of the above file types are suitable.
> The location of the index XML files [3], [4] has already been changed
> once (when projects-new was established).
>
> DOAP files are located all over the place and are often moved within
> the SCM without updating the index file.
> If they are located in the source tree there are often multiple copies
> in different branches.
>
> PMC RDF files may not be updateable except by the project (if located
> in their SCM), and again may move without warning if they are not in
> [2].
>
> It would potentially be possible to recover the PMC RDF files from
> their external locations and insist that they only be stored in the
> comdev area.
> But a single PMC may have multiple marks. Potentially also a project
> may move from a PMC to become its own PMC.
>
> Therefore I think a separate file is needed.
> That would also allow write access to be limited if necessary.

There are indeed multiple ways to solve this, and each way involves a tradeoff.

I would suggest separating this question into three parts.

- - -

First, where is the ultimate source for the data.  And the best way to
address that question is to first decide who will be updating that
data.  Will it be each project, or those on the branding mailing list,
or only VP brand?  Knowing the answer to that question will make a big
difference.

My suggestion would be to start simple with a single file, in the same
directory as committee-info.txt.  I'd suggest YAML as a format as it
is a good tradeoff between human edit-ability and programmatic
parse-ability.

- - -

Next is access.  What you need is something that takes the data from
the private repository, sanitizes it, and publishes the result for
public consumption.  Whimsy has a bunch of cron jobs that places
similar data here: https://whimsy.apache.org/public/.  A script that
parses a YAML file out of SVN, selects and filters out various parts,
and publishes the results in JSON format is very doable.

---

Finally, there is publishing.  While that could be a cron job that
produces static HTML, web browsers have the ability to consume JSON
and format the results.  That's probably the best solution to this.

---

The Apache Phone book is an example of an application that uses the
above design:

https://home.apache.org/phonebook.html

In fact, if the data is made available in this manner, the trademark
information could be included directly in the results of the page it
produces.  That's one of the nice things about having a public JSON
version of the data published - multiple tools can consume that data.

- Sam Ruby

>> The end result needs to be webcontent listing projects like:
>>
>> The ASF claims these trademarks
>> ...list all active TLPs
>> Apache {$projectname}
>> {$if registered then "" else ""}
>>
>> 
>>   {$shortdesc}
>> ...
>> The following projects are retired
>> ...list all Attic projects
>>
>> The following projects are in incubation; all trademarks here may be
>> property of respective owners
>> ...list all Incubation projects
>>
>> Separately, we should list the name of each software *product* here,
>> since if we offer something with a clear name as an independently
>> downloadable software product, it can be our trademark.  So I'd like to
>> list "Apache Directory Studio", since that's a notable name and a major
>> product.  But I don't want to list "Apache Commons Foo Bar Baz and
>> Kitchensink", since those are 

Apache Solr meetup

[Charlie Hull]

Hi,

I run the London Apache Lucene/Solr Meetup every two months and we have 
an event on Feb 22nd on "Learning to Rank with Solr & Hibernate and 
Lucene" 
http://www.meetup.com/Apache-Lucene-Solr-London-User-Group/events/226255641/ 
- would it be possible to add it to http://apache.org/events/meetups.html ?


Are there any other ways you might support or help our Meetup?

Best

Charlie

--
Charlie Hull
Flax - Open Source Enterprise Search

tel/fax: +44 (0)8700 118334
mobile:  +44 (0)7767 825828
web: www.flax.co.uk

Re: Adding asfext:registered to projects.a.o?

[Shane Curcuru]

Sam Ruby wrote on 2/11/16 12:28 PM:
> On Thu, Feb 11, 2016 at 11:35 AM, sebb  wrote:
>> On 11 February 2016 at 12:03, Shane Curcuru  wrote:
>>> I need to annotate our structured data set of Apache projects to track
>>> which project names are registered trademarks.  This is needed to be
>>> able to properly generate a.o/foundation/marks/list ...

...

>> Therefore I think a separate file is needed.
>> That would also allow write access to be limited if necessary.
> 
> There are indeed multiple ways to solve this, and each way involves a 
> tradeoff.
> 
> I would suggest separating this question into three parts.
> 
> - - -
> 
> First, where is the ultimate source for the data.  And the best way to
> address that question is to first decide who will be updating that
> data.  Will it be each project, or those on the branding mailing list,
> or only VP brand?  Knowing the answer to that question will make a big
> difference.
> 
> My suggestion would be to start simple with a single file, in the same
> directory as committee-info.txt.  I'd suggest YAML as a format as it
> is a good tradeoff between human edit-ability and programmatic
> parse-ability.

The raw data of which TLP names are registered can be public; it's
already findable in various national registries.  I may want to add an
additional enum "application-submitted", but even that can be public.

Theoretically just the brand committee should update the file, but in
reality we can restrict to members; I don't think they'll mess anything up.

The file won't change that often, but changes will be manual (i.e. when
we hear from counsel about applications).

> 
> - - -
> 
> Next is access.  What you need is something that takes the data from
> the private repository, sanitizes it, and publishes the result for
> public consumption.  Whimsy has a bunch of cron jobs that places
> similar data here: https://whimsy.apache.org/public/.  A script that
> parses a YAML file out of SVN, selects and filters out various parts,
> and publishes the results in JSON format is very doable.

It can go in a public repository if that makes it easier.  Of course,
this data isn't technically owned by any one project, so we need to find
a home for it, unless I should just dump it in the a.o site.

Is there any overall place for structured data about corporate
operations currently?
> 
> ---
> 
> Finally, there is publishing.  While that could be a cron job that
> produces static HTML, web browsers have the ability to consume JSON
> and format the results.  That's probably the best solution to this.

Thinking it through, we should fold this data into a number of places:

- The marks/list page, which needs to be regenerated each month after
the board meeting formally graduates or attics projects.  It likely has
low traffic to the page itself, but needs to be accurate, because
lawyers are the kind of people who will read it.

- projects.a.o, where it would be really nice to annotate project names
with the appropriate  and  symbols.  As this service becomes
more popular, having clear trademark indicators for our projects will
help ensure that third parties know (and can verify) that the ASF takes
it's trademarks seriously.

- www.a.o homepage, where whatever parts of the main site are generated
in any fashion include appropriate  and  symbols

I figure the first thing is to come up with schema and location of where
to put the source YAML/JSON file, then engineer the display into
marks/list or the main projects.a.o stuff.  Then see where to go from there.

> 
> ---
> 
> The Apache Phone book is an example of an application that uses the
> above design:
> 
> https://home.apache.org/phonebook.html
> 
> In fact, if the data is made available in this manner, the trademark
> information could be included directly in the results of the page it
> produces.  That's one of the nice things about having a public JSON
> version of the data published - multiple tools can consume that data.

Yeah, the more of these useful sites we have, it would be nice to fold
this in so it just gets automatically included.  It's especially
important for registered marks, because some countries require use of
the (R).

- Shane