incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan D. Cabrera" <l...@toolazydogs.com>
Subject Re: Tooling friendly incubator report
Date Wed, 03 Sep 2014 15:02:50 GMT

On Sep 2, 2014, at 5:49 PM, Roman Shaposhnik <roman@shaposhnik.org> wrote:

> On Sat, Aug 30, 2014 at 8:54 AM, Alan D. Cabrera <list@toolazydogs.com> wrote:
>> 
>> On Aug 24, 2014, at 2:16 PM, Roman Shaposhnik <roman@shaposhnik.org> wrote:
>> 
>>> On Sun, Aug 24, 2014 at 1:54 PM, Alan D. Cabrera <list@toolazydogs.com>
wrote:
>>>>> but its just my opinion, and if incubator is used to work differently,
I
>>>>> will not be the one to propose big changes.
>>>> 
>>>> This is pretty much how it works now.  As I mentioned above, I am merely
proposing
>>>> that we use a more structured YAML file instead of a wiki page.
>>> 
>>> On that note: I *really* would like to start using YAMLized version
>>> for our Sep report.
>> 
>> I think that we'll stick w/ the wiki for September's report.  We need to work out
things like where to put the YAML file.
> 
> Can I make a suggestion, please?
> 
> Would it be too much to ask to have YAML report *in addition*
> with the regular wiki?

Keeping the YAML file in sync with the free form wiki would be very difficult.  

IMO, having both would be confusing.

> We should be absolutely clear that it is auxiliary, but I think
> it will be a useful way for poddlings to familiarize themselves
> with the structure of the YAML file and ease the transition
> later on.

Working with a YAML file will not be too difficult for podlings; this is a technical community.

>> Where should we put the YAML file.  It needs to be in a place where all committers
have R/W access.  I was thinking:
>> 
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/data/reports
> 
> This looks like as good place as any. Besides, changing that location
> is one svn mv away ;-)

Do podling committers have R/W access?


Regards,
Alan



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message