Re: ApacheCon EU: What I need help with

Hi Rich, On 09/07/14 19:05, Rich Bowen wrote: Sergio, as we've discussed off list, if you can put together a compelling topic based track, please do so. The list you put together earlier looks great. Lets make that a tab in the spreadsheet. As we talked, The Linked Data tab in the spreadsheet

Re: ApacheCon EU: What I need help with

On Tue, Jul 8, 2014 at 9:49 AM, Rich Bowen wrote: > Thank you all for your enormous help so far. I can still use some help if > we're going to make a *July 15th* deadline for CFP notifications. Here's > what you can still do: > > The spreadsheet is at *http://tm3.org/aceu2014tracks* > > > * Check

Re: Proposing for Apache Member?

Try reading http://www.apache.org/foundation/how-it-works.html On 9 Jul 2014 22:20, "Pierre Smits" wrote: > It is a bit strange to read that 'Contributor' is not the official role for > anybody who is committed to an Apache project. Equally strange is it to > read that both the 'User' and the 'De

Re: Proposing for Apache Member?

It is a bit strange to read that 'Contributor' is not the official role for anybody who is committed to an Apache project. Equally strange is it to read that both the 'User' and the 'Developer' is defined/explained as the person who is contributing. Pierre Smits *ORRTIZ.COM

Re: ApacheCon EU: What I need help with

Sergio, as we've discussed off list, if you can put together a compelling topic based track, please do so. The list you put together earlier looks great. Lets make that a tab in the spreadsheet. -- Rich Bowen, mobile edition rbo...@rcbowen.com On Jul 9, 2014 8:37 AM, "Sergio Fernández" wrote: >

Re: ApacheCon EU: What I need help with

Hi Rich, On 08/07/14 18:49, Rich Bowen wrote: * Check the first tab. If something isn't in a track (ie, isn't color coded in any way), put it in one. Even if it's a track with only one thing in it. Otherwise it might get overlooked later on. Regarding the Linked Data track, there are some prop

Re: ApacheCon EU: What I need help with

On Jul 8, 2014 1:12 PM, "Pierre Smits" wrote: > > Hi Rich, > > That first link that you included redirects to http://tm3.org > > ... > > > > The spreadsheet is at *http://tm3.org/aceu2014tracks* Looks like Thunderbird added asterisks around the link. Weird. Try without. http://tm3.org/aceu2014

Re: Understanding the commit-then-review workflow

A practical example of a technical veto I've seen was when we added some new optimisations that interacted badly with a pre-existing API in some rare corner cases. This actually went into a release and it wasn't until a particularly vocal community member got round to upgrading that we became awar

Re: Understanding the commit-then-review workflow

I think the vetoing -1 from PMCs is mainly used for 'legal' reasons. If e.g. some new committer adds code which he took from an external project and it's license is not appropriate. I've not yet seen -1 for purely technical reasons. This might happen. But usually a consensus is reached after the