You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rya.apache.org by Sean Busbey <bu...@apache.org> on 2016/02/23 21:18:26 UTC
Looking towards our next IPMC report
Heya Rya!
We're about 5-6 weeks from our next scheduled turn for the IPMC's board report.
How are folks doing? The project sounds a bit quiet to me, but I'm not
sure how much of that is me being sure to look in the right places.
To Review, here are your self-identified three most important objectives:
1. Populate the website for the project
2. Expand the "how to" document to explain the ways new contributors can
become involved in the project, so we increase the size of the
community.
3. Become familiar with the release process and have a first release as
part of the Apache Foundation
At least to me, numbers 1 and 3 seem like big barriers to getting new
folks brought in. Anyone have a list of the blockers keeping us from
those two? I tried searching the jira for relevant tickets, but didn't
find any.
-Sean
Re: Looking towards our next IPMC report
Posted by "Aaron D. Mihalik" <aa...@gmail.com>.
Thanks. I've started putting together notes on our wiki:
https://cwiki.apache.org/confluence/display/RYA/How+To+Release+Rya
On Thu, Apr 7, 2016 at 12:26 PM Seetharam Venkatesh <ve...@innerzeal.com>
wrote:
> I have followed this and have been quite successful, thanks to Jarec for
> putting this together.
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release+Sqoop2
>
> Thanks!
>
> On Thu, Apr 7, 2016 at 9:00 AM Sean Busbey <bu...@apache.org> wrote:
>
> > So long as we're plugging other project release guides ;)
> >
> > http://yetus.apache.org/contribute/releases/
> >
> > On Thu, Apr 7, 2016 at 8:18 AM, Josh Elser <jo...@gmail.com> wrote:
> > > Yay. If I can offer my $0.02:
> > >
> > > * As you go through the process the first time, update the website
> > > immediately. Every little step you do, write it down (this will make
> sure
> > > that you're not the only person to be able to make a release).
> > > * Automate as much as you possibly can. Ideally, your process should be
> > `mvn
> > > release:prepare && mvn release:perform` as a Maven project.
> > > * Try to take some help from other projects [1], [2], [3] for starters.
> > > * Ask questions if you get stuck :)
> > >
> > > - Josh
> > >
> > > [1] http://accumulo.apache.org/releasing.html
> > > [2] http://accumulo.apache.org/verifying_releases.html
> > > [3] http://nifi.apache.org/release-guide.html
> > >
> > >
> > > Aaron D. Mihalik wrote:
> > >>
> > >> Josh/Venkatesh: I'll take RM for our first release. David put a lot of
> > >> effort in researching this process, so I'll look through his notes
> over
> > >> the
> > >> weekend, start the process, and ping the dev list with questions.
> > >>
> > >> Thanks again for your help.
> > >>
> > >> --Aaron
> > >> On Wed, Apr 6, 2016 at 5:55 PM Josh Elser<jo...@gmail.com>
> wrote:
> > >>
> > >>> +1 to Venkatesh's overall message (if I can put words in mouths):
> don't
> > >>> get too hung up on "perfect the first time". Showing progress is much
> > >>> more important.
> > >>>
> > >>> Seetharam Venkatesh wrote:
> > >>>>
> > >>>> Thanks Adina, report looks good. There are quite a few low hanging
> > >>>> issues
> > >>>> that can be addressed quickly.
> > >>>>
> > >>>>> Become familiar with the release process and have a first release
> as
> > >>>
> > >>> part
> > >>>>
> > >>>> of the Apache Foundation
> > >>>> I have done about 5 incubating releases and can help if someone can
> > >>>> volunteer as an RM. This is not hard and its an easy win for a
> > podling.
> > >>>>
> > >>>>> Expand the "how to" document to explain the ways new contributors
> can
> > >>>>
> > >>>> become involved in the project
> > >>>> This can start simple and can be iterated. You can also look at what
> > >>>
> > >>> other
> > >>>>
> > >>>> incubating projects are doing.
> > >>>>
> > >>>>> We have a Rya "office hour" teleconference every other week
> > >>>>
> > >>>> Can you also please put this on the confluence wiki so its
> accessible.
> > >>>>
> > >>>> Thanks!
> > >>>> Venkatesh
> > >>>>
> > >>>> On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu<ad...@usna.edu>
> > >>>
> > >>> wrote:
> > >>>>>
> > >>>>> I submitted the report. Sorry for waiting till the last minute - I
> > >>>
> > >>> wanted
> > >>>>>
> > >>>>> to have a website first :)
> > >>>>>
> > >>>>> Thank you,
> > >>>>> Adina
> > >>>>>
> > >>>>> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh<
> > >>>>> venkatesh@innerzeal.com
> > >>>>>>
> > >>>>>> wrote:
> > >>>>>> Hey folks, the report is to be signed off today and I do not see
> it
> > >>>
> > >>> being
> > >>>>>>
> > >>>>>> filled at http://wiki.apache.org/incubator/April2016.
> > >>>>>>
> > >>>>>> Appreciate if one of you could take care of this asap.
> > >>>>>>
> > >>>>>> Thanks!
> > >>>>>> Venkatesh
> > >>>>>>
> > >>>>>> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey<bu...@apache.org>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> For those interested in posting feedback, the website jira is
> > RYA-42
> > >>>>>>>
> > >>>>>>> On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu<
> adina@usna.edu>
> > >>>>>>
> > >>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>> I created a JIRA ticket for the website. If anyone has specific
> > >>>>>>>> ideas
> > >>>>>>
> > >>>>>> for
> > >>>>>>>>
> > >>>>>>>> it, please fell free to mention/implement them. Otherwise I'll
> try
> > >>>>>>>> to
> > >>>>>>>> use/customize the apache-website-template available at
> > >>>>>>>> https://github.com/apache/apache-website-template/ as soon as
> > >>>>>>
> > >>>>>> possible,
> > >>>>>>>
> > >>>>>>> but
> > >>>>>>>>
> > >>>>>>>> definitely before the next report is due
> > >>>>>>>>
> > >>>>>>>> Adina
> > >>>>>>>>
> > >>>>>>>> On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil<
> pujav65@gmail.com>
> > >>>>>>>
> > >>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>> David and I tried to compile a process for creating a release
> --
> > we
> > >>>>>>>
> > >>>>>>> didn't
> > >>>>>>>>>
> > >>>>>>>>> get that far. The main thing blocking us at this point is the
> > >>>>>>>>> whole
> > >>>>>>>>> process for signing a release, no one we knew had a public key
> > and
> > >>>>>>
> > >>>>>> then
> > >>>>>>>>>
> > >>>>>>>>> David and I got lost/confused when trying to generate and
> > register
> > >>>>>>
> > >>>>>> one.
> > >>>>>>>>>
> > >>>>>>>>> All of this sounds borderline embarrassing since there is a lot
> > of
> > >>>>>>>>> documentation out there but we didn't have time to fully digest
> > it
> > >>>>>
> > >>>>> in
> > >>>>>>>>>
> > >>>>>>>>> time.
> > >>>>>>>>> I'm also not clear on what else we would need to do besides run
> > mvn
> > >>>>>>>>> release, like compile release notes, etc. I'm sorry if
> there's a
> > >>>>>
> > >>>>> lot
> > >>>>>>
> > >>>>>> of
> > >>>>>>>>>
> > >>>>>>>>> documentation exactly detailing what we need to do.
> > >>>>>>>>> Other than that, I think we've made a lot of progress as a
> > >>>>>>>>> community
> > >>>>>>>
> > >>>>>>> this
> > >>>>>>>>>
> > >>>>>>>>> past month. We've had a lot of new contributors, had a lot of
> > new
> > >>>>>>
> > >>>>>> bugs
> > >>>>>>>>>
> > >>>>>>>>> reported by new end users, and have closed out a lot of issues.
> > >>>>>>>>>
> > >>>>>>>>> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey<busbey@apache.org
> >
> > >>>>>>
> > >>>>>> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>> Heya Rya!
> > >>>>>>>>>>
> > >>>>>>>>>> We're about 5-6 weeks from our next scheduled turn for the
> > IPMC's
> > >>>>>>>
> > >>>>>>> board
> > >>>>>>>>>>
> > >>>>>>>>>> report.
> > >>>>>>>>>>
> > >>>>>>>>>> How are folks doing? The project sounds a bit quiet to me, but
> > I'm
> > >>>>>>
> > >>>>>> not
> > >>>>>>>>>>
> > >>>>>>>>>> sure how much of that is me being sure to look in the right
> > >>>>>
> > >>>>> places.
> > >>>>>>>>>>
> > >>>>>>>>>> To Review, here are your self-identified three most important
> > >>>>>>>
> > >>>>>>> objectives:
> > >>>>>>>>>>
> > >>>>>>>>>> 1. Populate the website for the project
> > >>>>>>>>>> 2. Expand the "how to" document to explain the ways new
> > >>>>>>
> > >>>>>> contributors
> > >>>>>>>>>
> > >>>>>>>>> can
> > >>>>>>>>>>
> > >>>>>>>>>> become involved in the project, so we increase the size
> > of
> > >>>>>
> > >>>>> the
> > >>>>>>>>>>
> > >>>>>>>>>> community.
> > >>>>>>>>>> 3. Become familiar with the release process and have a
> first
> > >>>>>>>
> > >>>>>>> release as
> > >>>>>>>>>>
> > >>>>>>>>>> part of the Apache Foundation
> > >>>>>>>>>>
> > >>>>>>>>>> At least to me, numbers 1 and 3 seem like big barriers to
> > getting
> > >>>>>>
> > >>>>>> new
> > >>>>>>>>>>
> > >>>>>>>>>> folks brought in. Anyone have a list of the blockers keeping
> us
> > >>>>>
> > >>>>> from
> > >>>>>>>>>>
> > >>>>>>>>>> those two? I tried searching the jira for relevant tickets,
> but
> > >>>>>>
> > >>>>>> didn't
> > >>>>>>>>>>
> > >>>>>>>>>> find any.
> > >>>>>>>>>>
> > >>>>>>>>>> -Sean
> > >>>>>>>>>>
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Dr. Adina Crainiceanu
> > >>>>>>>> http://www.usna.edu/Users/cs/adina/
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Dr. Adina Crainiceanu
> > >>>>> http://www.usna.edu/Users/cs/adina/
> > >>>>>
> > >>
> > >
> >
>
Re: Looking towards our next IPMC report
Posted by Seetharam Venkatesh <ve...@innerzeal.com>.
I have followed this and have been quite successful, thanks to Jarec for
putting this together.
https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release+Sqoop2
Thanks!
On Thu, Apr 7, 2016 at 9:00 AM Sean Busbey <bu...@apache.org> wrote:
> So long as we're plugging other project release guides ;)
>
> http://yetus.apache.org/contribute/releases/
>
> On Thu, Apr 7, 2016 at 8:18 AM, Josh Elser <jo...@gmail.com> wrote:
> > Yay. If I can offer my $0.02:
> >
> > * As you go through the process the first time, update the website
> > immediately. Every little step you do, write it down (this will make sure
> > that you're not the only person to be able to make a release).
> > * Automate as much as you possibly can. Ideally, your process should be
> `mvn
> > release:prepare && mvn release:perform` as a Maven project.
> > * Try to take some help from other projects [1], [2], [3] for starters.
> > * Ask questions if you get stuck :)
> >
> > - Josh
> >
> > [1] http://accumulo.apache.org/releasing.html
> > [2] http://accumulo.apache.org/verifying_releases.html
> > [3] http://nifi.apache.org/release-guide.html
> >
> >
> > Aaron D. Mihalik wrote:
> >>
> >> Josh/Venkatesh: I'll take RM for our first release. David put a lot of
> >> effort in researching this process, so I'll look through his notes over
> >> the
> >> weekend, start the process, and ping the dev list with questions.
> >>
> >> Thanks again for your help.
> >>
> >> --Aaron
> >> On Wed, Apr 6, 2016 at 5:55 PM Josh Elser<jo...@gmail.com> wrote:
> >>
> >>> +1 to Venkatesh's overall message (if I can put words in mouths): don't
> >>> get too hung up on "perfect the first time". Showing progress is much
> >>> more important.
> >>>
> >>> Seetharam Venkatesh wrote:
> >>>>
> >>>> Thanks Adina, report looks good. There are quite a few low hanging
> >>>> issues
> >>>> that can be addressed quickly.
> >>>>
> >>>>> Become familiar with the release process and have a first release as
> >>>
> >>> part
> >>>>
> >>>> of the Apache Foundation
> >>>> I have done about 5 incubating releases and can help if someone can
> >>>> volunteer as an RM. This is not hard and its an easy win for a
> podling.
> >>>>
> >>>>> Expand the "how to" document to explain the ways new contributors can
> >>>>
> >>>> become involved in the project
> >>>> This can start simple and can be iterated. You can also look at what
> >>>
> >>> other
> >>>>
> >>>> incubating projects are doing.
> >>>>
> >>>>> We have a Rya "office hour" teleconference every other week
> >>>>
> >>>> Can you also please put this on the confluence wiki so its accessible.
> >>>>
> >>>> Thanks!
> >>>> Venkatesh
> >>>>
> >>>> On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu<ad...@usna.edu>
> >>>
> >>> wrote:
> >>>>>
> >>>>> I submitted the report. Sorry for waiting till the last minute - I
> >>>
> >>> wanted
> >>>>>
> >>>>> to have a website first :)
> >>>>>
> >>>>> Thank you,
> >>>>> Adina
> >>>>>
> >>>>> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh<
> >>>>> venkatesh@innerzeal.com
> >>>>>>
> >>>>>> wrote:
> >>>>>> Hey folks, the report is to be signed off today and I do not see it
> >>>
> >>> being
> >>>>>>
> >>>>>> filled at http://wiki.apache.org/incubator/April2016.
> >>>>>>
> >>>>>> Appreciate if one of you could take care of this asap.
> >>>>>>
> >>>>>> Thanks!
> >>>>>> Venkatesh
> >>>>>>
> >>>>>> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey<bu...@apache.org>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> For those interested in posting feedback, the website jira is
> RYA-42
> >>>>>>>
> >>>>>>> On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu<ad...@usna.edu>
> >>>>>>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>> I created a JIRA ticket for the website. If anyone has specific
> >>>>>>>> ideas
> >>>>>>
> >>>>>> for
> >>>>>>>>
> >>>>>>>> it, please fell free to mention/implement them. Otherwise I'll try
> >>>>>>>> to
> >>>>>>>> use/customize the apache-website-template available at
> >>>>>>>> https://github.com/apache/apache-website-template/ as soon as
> >>>>>>
> >>>>>> possible,
> >>>>>>>
> >>>>>>> but
> >>>>>>>>
> >>>>>>>> definitely before the next report is due
> >>>>>>>>
> >>>>>>>> Adina
> >>>>>>>>
> >>>>>>>> On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil<pu...@gmail.com>
> >>>>>>>
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> David and I tried to compile a process for creating a release --
> we
> >>>>>>>
> >>>>>>> didn't
> >>>>>>>>>
> >>>>>>>>> get that far. The main thing blocking us at this point is the
> >>>>>>>>> whole
> >>>>>>>>> process for signing a release, no one we knew had a public key
> and
> >>>>>>
> >>>>>> then
> >>>>>>>>>
> >>>>>>>>> David and I got lost/confused when trying to generate and
> register
> >>>>>>
> >>>>>> one.
> >>>>>>>>>
> >>>>>>>>> All of this sounds borderline embarrassing since there is a lot
> of
> >>>>>>>>> documentation out there but we didn't have time to fully digest
> it
> >>>>>
> >>>>> in
> >>>>>>>>>
> >>>>>>>>> time.
> >>>>>>>>> I'm also not clear on what else we would need to do besides run
> mvn
> >>>>>>>>> release, like compile release notes, etc. I'm sorry if there's a
> >>>>>
> >>>>> lot
> >>>>>>
> >>>>>> of
> >>>>>>>>>
> >>>>>>>>> documentation exactly detailing what we need to do.
> >>>>>>>>> Other than that, I think we've made a lot of progress as a
> >>>>>>>>> community
> >>>>>>>
> >>>>>>> this
> >>>>>>>>>
> >>>>>>>>> past month. We've had a lot of new contributors, had a lot of
> new
> >>>>>>
> >>>>>> bugs
> >>>>>>>>>
> >>>>>>>>> reported by new end users, and have closed out a lot of issues.
> >>>>>>>>>
> >>>>>>>>> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey<bu...@apache.org>
> >>>>>>
> >>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Heya Rya!
> >>>>>>>>>>
> >>>>>>>>>> We're about 5-6 weeks from our next scheduled turn for the
> IPMC's
> >>>>>>>
> >>>>>>> board
> >>>>>>>>>>
> >>>>>>>>>> report.
> >>>>>>>>>>
> >>>>>>>>>> How are folks doing? The project sounds a bit quiet to me, but
> I'm
> >>>>>>
> >>>>>> not
> >>>>>>>>>>
> >>>>>>>>>> sure how much of that is me being sure to look in the right
> >>>>>
> >>>>> places.
> >>>>>>>>>>
> >>>>>>>>>> To Review, here are your self-identified three most important
> >>>>>>>
> >>>>>>> objectives:
> >>>>>>>>>>
> >>>>>>>>>> 1. Populate the website for the project
> >>>>>>>>>> 2. Expand the "how to" document to explain the ways new
> >>>>>>
> >>>>>> contributors
> >>>>>>>>>
> >>>>>>>>> can
> >>>>>>>>>>
> >>>>>>>>>> become involved in the project, so we increase the size
> of
> >>>>>
> >>>>> the
> >>>>>>>>>>
> >>>>>>>>>> community.
> >>>>>>>>>> 3. Become familiar with the release process and have a first
> >>>>>>>
> >>>>>>> release as
> >>>>>>>>>>
> >>>>>>>>>> part of the Apache Foundation
> >>>>>>>>>>
> >>>>>>>>>> At least to me, numbers 1 and 3 seem like big barriers to
> getting
> >>>>>>
> >>>>>> new
> >>>>>>>>>>
> >>>>>>>>>> folks brought in. Anyone have a list of the blockers keeping us
> >>>>>
> >>>>> from
> >>>>>>>>>>
> >>>>>>>>>> those two? I tried searching the jira for relevant tickets, but
> >>>>>>
> >>>>>> didn't
> >>>>>>>>>>
> >>>>>>>>>> find any.
> >>>>>>>>>>
> >>>>>>>>>> -Sean
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Dr. Adina Crainiceanu
> >>>>>>>> http://www.usna.edu/Users/cs/adina/
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Dr. Adina Crainiceanu
> >>>>> http://www.usna.edu/Users/cs/adina/
> >>>>>
> >>
> >
>
Re: Looking towards our next IPMC report
Posted by Sean Busbey <bu...@apache.org>.
So long as we're plugging other project release guides ;)
http://yetus.apache.org/contribute/releases/
On Thu, Apr 7, 2016 at 8:18 AM, Josh Elser <jo...@gmail.com> wrote:
> Yay. If I can offer my $0.02:
>
> * As you go through the process the first time, update the website
> immediately. Every little step you do, write it down (this will make sure
> that you're not the only person to be able to make a release).
> * Automate as much as you possibly can. Ideally, your process should be `mvn
> release:prepare && mvn release:perform` as a Maven project.
> * Try to take some help from other projects [1], [2], [3] for starters.
> * Ask questions if you get stuck :)
>
> - Josh
>
> [1] http://accumulo.apache.org/releasing.html
> [2] http://accumulo.apache.org/verifying_releases.html
> [3] http://nifi.apache.org/release-guide.html
>
>
> Aaron D. Mihalik wrote:
>>
>> Josh/Venkatesh: I'll take RM for our first release. David put a lot of
>> effort in researching this process, so I'll look through his notes over
>> the
>> weekend, start the process, and ping the dev list with questions.
>>
>> Thanks again for your help.
>>
>> --Aaron
>> On Wed, Apr 6, 2016 at 5:55 PM Josh Elser<jo...@gmail.com> wrote:
>>
>>> +1 to Venkatesh's overall message (if I can put words in mouths): don't
>>> get too hung up on "perfect the first time". Showing progress is much
>>> more important.
>>>
>>> Seetharam Venkatesh wrote:
>>>>
>>>> Thanks Adina, report looks good. There are quite a few low hanging
>>>> issues
>>>> that can be addressed quickly.
>>>>
>>>>> Become familiar with the release process and have a first release as
>>>
>>> part
>>>>
>>>> of the Apache Foundation
>>>> I have done about 5 incubating releases and can help if someone can
>>>> volunteer as an RM. This is not hard and its an easy win for a podling.
>>>>
>>>>> Expand the "how to" document to explain the ways new contributors can
>>>>
>>>> become involved in the project
>>>> This can start simple and can be iterated. You can also look at what
>>>
>>> other
>>>>
>>>> incubating projects are doing.
>>>>
>>>>> We have a Rya "office hour" teleconference every other week
>>>>
>>>> Can you also please put this on the confluence wiki so its accessible.
>>>>
>>>> Thanks!
>>>> Venkatesh
>>>>
>>>> On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu<ad...@usna.edu>
>>>
>>> wrote:
>>>>>
>>>>> I submitted the report. Sorry for waiting till the last minute - I
>>>
>>> wanted
>>>>>
>>>>> to have a website first :)
>>>>>
>>>>> Thank you,
>>>>> Adina
>>>>>
>>>>> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh<
>>>>> venkatesh@innerzeal.com
>>>>>>
>>>>>> wrote:
>>>>>> Hey folks, the report is to be signed off today and I do not see it
>>>
>>> being
>>>>>>
>>>>>> filled at http://wiki.apache.org/incubator/April2016.
>>>>>>
>>>>>> Appreciate if one of you could take care of this asap.
>>>>>>
>>>>>> Thanks!
>>>>>> Venkatesh
>>>>>>
>>>>>> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey<bu...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> For those interested in posting feedback, the website jira is RYA-42
>>>>>>>
>>>>>>> On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu<ad...@usna.edu>
>>>>>>
>>>>>> wrote:
>>>>>>>>
>>>>>>>> I created a JIRA ticket for the website. If anyone has specific
>>>>>>>> ideas
>>>>>>
>>>>>> for
>>>>>>>>
>>>>>>>> it, please fell free to mention/implement them. Otherwise I'll try
>>>>>>>> to
>>>>>>>> use/customize the apache-website-template available at
>>>>>>>> https://github.com/apache/apache-website-template/ as soon as
>>>>>>
>>>>>> possible,
>>>>>>>
>>>>>>> but
>>>>>>>>
>>>>>>>> definitely before the next report is due
>>>>>>>>
>>>>>>>> Adina
>>>>>>>>
>>>>>>>> On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil<pu...@gmail.com>
>>>>>>>
>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> David and I tried to compile a process for creating a release -- we
>>>>>>>
>>>>>>> didn't
>>>>>>>>>
>>>>>>>>> get that far. The main thing blocking us at this point is the
>>>>>>>>> whole
>>>>>>>>> process for signing a release, no one we knew had a public key and
>>>>>>
>>>>>> then
>>>>>>>>>
>>>>>>>>> David and I got lost/confused when trying to generate and register
>>>>>>
>>>>>> one.
>>>>>>>>>
>>>>>>>>> All of this sounds borderline embarrassing since there is a lot of
>>>>>>>>> documentation out there but we didn't have time to fully digest it
>>>>>
>>>>> in
>>>>>>>>>
>>>>>>>>> time.
>>>>>>>>> I'm also not clear on what else we would need to do besides run mvn
>>>>>>>>> release, like compile release notes, etc. I'm sorry if there's a
>>>>>
>>>>> lot
>>>>>>
>>>>>> of
>>>>>>>>>
>>>>>>>>> documentation exactly detailing what we need to do.
>>>>>>>>> Other than that, I think we've made a lot of progress as a
>>>>>>>>> community
>>>>>>>
>>>>>>> this
>>>>>>>>>
>>>>>>>>> past month. We've had a lot of new contributors, had a lot of new
>>>>>>
>>>>>> bugs
>>>>>>>>>
>>>>>>>>> reported by new end users, and have closed out a lot of issues.
>>>>>>>>>
>>>>>>>>> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey<bu...@apache.org>
>>>>>>
>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Heya Rya!
>>>>>>>>>>
>>>>>>>>>> We're about 5-6 weeks from our next scheduled turn for the IPMC's
>>>>>>>
>>>>>>> board
>>>>>>>>>>
>>>>>>>>>> report.
>>>>>>>>>>
>>>>>>>>>> How are folks doing? The project sounds a bit quiet to me, but I'm
>>>>>>
>>>>>> not
>>>>>>>>>>
>>>>>>>>>> sure how much of that is me being sure to look in the right
>>>>>
>>>>> places.
>>>>>>>>>>
>>>>>>>>>> To Review, here are your self-identified three most important
>>>>>>>
>>>>>>> objectives:
>>>>>>>>>>
>>>>>>>>>> 1. Populate the website for the project
>>>>>>>>>> 2. Expand the "how to" document to explain the ways new
>>>>>>
>>>>>> contributors
>>>>>>>>>
>>>>>>>>> can
>>>>>>>>>>
>>>>>>>>>> become involved in the project, so we increase the size of
>>>>>
>>>>> the
>>>>>>>>>>
>>>>>>>>>> community.
>>>>>>>>>> 3. Become familiar with the release process and have a first
>>>>>>>
>>>>>>> release as
>>>>>>>>>>
>>>>>>>>>> part of the Apache Foundation
>>>>>>>>>>
>>>>>>>>>> At least to me, numbers 1 and 3 seem like big barriers to getting
>>>>>>
>>>>>> new
>>>>>>>>>>
>>>>>>>>>> folks brought in. Anyone have a list of the blockers keeping us
>>>>>
>>>>> from
>>>>>>>>>>
>>>>>>>>>> those two? I tried searching the jira for relevant tickets, but
>>>>>>
>>>>>> didn't
>>>>>>>>>>
>>>>>>>>>> find any.
>>>>>>>>>>
>>>>>>>>>> -Sean
>>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Dr. Adina Crainiceanu
>>>>>>>> http://www.usna.edu/Users/cs/adina/
>>>>>
>>>>>
>>>>> --
>>>>> Dr. Adina Crainiceanu
>>>>> http://www.usna.edu/Users/cs/adina/
>>>>>
>>
>
Re: Looking towards our next IPMC report
Posted by Josh Elser <jo...@gmail.com>.
Yay. If I can offer my $0.02:
* As you go through the process the first time, update the website
immediately. Every little step you do, write it down (this will make
sure that you're not the only person to be able to make a release).
* Automate as much as you possibly can. Ideally, your process should be
`mvn release:prepare && mvn release:perform` as a Maven project.
* Try to take some help from other projects [1], [2], [3] for starters.
* Ask questions if you get stuck :)
- Josh
[1] http://accumulo.apache.org/releasing.html
[2] http://accumulo.apache.org/verifying_releases.html
[3] http://nifi.apache.org/release-guide.html
Aaron D. Mihalik wrote:
> Josh/Venkatesh: I'll take RM for our first release. David put a lot of
> effort in researching this process, so I'll look through his notes over the
> weekend, start the process, and ping the dev list with questions.
>
> Thanks again for your help.
>
> --Aaron
> On Wed, Apr 6, 2016 at 5:55 PM Josh Elser<jo...@gmail.com> wrote:
>
>> +1 to Venkatesh's overall message (if I can put words in mouths): don't
>> get too hung up on "perfect the first time". Showing progress is much
>> more important.
>>
>> Seetharam Venkatesh wrote:
>>> Thanks Adina, report looks good. There are quite a few low hanging issues
>>> that can be addressed quickly.
>>>
>>>> Become familiar with the release process and have a first release as
>> part
>>> of the Apache Foundation
>>> I have done about 5 incubating releases and can help if someone can
>>> volunteer as an RM. This is not hard and its an easy win for a podling.
>>>
>>>> Expand the "how to" document to explain the ways new contributors can
>>> become involved in the project
>>> This can start simple and can be iterated. You can also look at what
>> other
>>> incubating projects are doing.
>>>
>>>> We have a Rya "office hour" teleconference every other week
>>> Can you also please put this on the confluence wiki so its accessible.
>>>
>>> Thanks!
>>> Venkatesh
>>>
>>> On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu<ad...@usna.edu>
>> wrote:
>>>> I submitted the report. Sorry for waiting till the last minute - I
>> wanted
>>>> to have a website first :)
>>>>
>>>> Thank you,
>>>> Adina
>>>>
>>>> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh<
>>>> venkatesh@innerzeal.com
>>>>> wrote:
>>>>> Hey folks, the report is to be signed off today and I do not see it
>> being
>>>>> filled at http://wiki.apache.org/incubator/April2016.
>>>>>
>>>>> Appreciate if one of you could take care of this asap.
>>>>>
>>>>> Thanks!
>>>>> Venkatesh
>>>>>
>>>>> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey<bu...@apache.org> wrote:
>>>>>
>>>>>> For those interested in posting feedback, the website jira is RYA-42
>>>>>>
>>>>>> On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu<ad...@usna.edu>
>>>>> wrote:
>>>>>>> I created a JIRA ticket for the website. If anyone has specific ideas
>>>>> for
>>>>>>> it, please fell free to mention/implement them. Otherwise I'll try to
>>>>>>> use/customize the apache-website-template available at
>>>>>>> https://github.com/apache/apache-website-template/ as soon as
>>>>> possible,
>>>>>> but
>>>>>>> definitely before the next report is due
>>>>>>>
>>>>>>> Adina
>>>>>>>
>>>>>>> On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil<pu...@gmail.com>
>>>>>> wrote:
>>>>>>>> David and I tried to compile a process for creating a release -- we
>>>>>> didn't
>>>>>>>> get that far. The main thing blocking us at this point is the whole
>>>>>>>> process for signing a release, no one we knew had a public key and
>>>>> then
>>>>>>>> David and I got lost/confused when trying to generate and register
>>>>> one.
>>>>>>>> All of this sounds borderline embarrassing since there is a lot of
>>>>>>>> documentation out there but we didn't have time to fully digest it
>>>> in
>>>>>>>> time.
>>>>>>>> I'm also not clear on what else we would need to do besides run mvn
>>>>>>>> release, like compile release notes, etc. I'm sorry if there's a
>>>> lot
>>>>> of
>>>>>>>> documentation exactly detailing what we need to do.
>>>>>>>> Other than that, I think we've made a lot of progress as a community
>>>>>> this
>>>>>>>> past month. We've had a lot of new contributors, had a lot of new
>>>>> bugs
>>>>>>>> reported by new end users, and have closed out a lot of issues.
>>>>>>>>
>>>>>>>> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey<bu...@apache.org>
>>>>> wrote:
>>>>>>>>> Heya Rya!
>>>>>>>>>
>>>>>>>>> We're about 5-6 weeks from our next scheduled turn for the IPMC's
>>>>>> board
>>>>>>>>> report.
>>>>>>>>>
>>>>>>>>> How are folks doing? The project sounds a bit quiet to me, but I'm
>>>>> not
>>>>>>>>> sure how much of that is me being sure to look in the right
>>>> places.
>>>>>>>>> To Review, here are your self-identified three most important
>>>>>> objectives:
>>>>>>>>> 1. Populate the website for the project
>>>>>>>>> 2. Expand the "how to" document to explain the ways new
>>>>> contributors
>>>>>>>> can
>>>>>>>>> become involved in the project, so we increase the size of
>>>> the
>>>>>>>>> community.
>>>>>>>>> 3. Become familiar with the release process and have a first
>>>>>> release as
>>>>>>>>> part of the Apache Foundation
>>>>>>>>>
>>>>>>>>> At least to me, numbers 1 and 3 seem like big barriers to getting
>>>>> new
>>>>>>>>> folks brought in. Anyone have a list of the blockers keeping us
>>>> from
>>>>>>>>> those two? I tried searching the jira for relevant tickets, but
>>>>> didn't
>>>>>>>>> find any.
>>>>>>>>>
>>>>>>>>> -Sean
>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Dr. Adina Crainiceanu
>>>>>>> http://www.usna.edu/Users/cs/adina/
>>>>
>>>> --
>>>> Dr. Adina Crainiceanu
>>>> http://www.usna.edu/Users/cs/adina/
>>>>
>
Re: Looking towards our next IPMC report
Posted by "Aaron D. Mihalik" <aa...@gmail.com>.
Josh/Venkatesh: I'll take RM for our first release. David put a lot of
effort in researching this process, so I'll look through his notes over the
weekend, start the process, and ping the dev list with questions.
Thanks again for your help.
--Aaron
On Wed, Apr 6, 2016 at 5:55 PM Josh Elser <jo...@gmail.com> wrote:
> +1 to Venkatesh's overall message (if I can put words in mouths): don't
> get too hung up on "perfect the first time". Showing progress is much
> more important.
>
> Seetharam Venkatesh wrote:
> > Thanks Adina, report looks good. There are quite a few low hanging issues
> > that can be addressed quickly.
> >
> >> Become familiar with the release process and have a first release as
> part
> > of the Apache Foundation
> > I have done about 5 incubating releases and can help if someone can
> > volunteer as an RM. This is not hard and its an easy win for a podling.
> >
> >> Expand the "how to" document to explain the ways new contributors can
> > become involved in the project
> > This can start simple and can be iterated. You can also look at what
> other
> > incubating projects are doing.
> >
> >> We have a Rya "office hour" teleconference every other week
> > Can you also please put this on the confluence wiki so its accessible.
> >
> > Thanks!
> > Venkatesh
> >
> > On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu<ad...@usna.edu>
> wrote:
> >
> >> I submitted the report. Sorry for waiting till the last minute - I
> wanted
> >> to have a website first :)
> >>
> >> Thank you,
> >> Adina
> >>
> >> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh<
> >> venkatesh@innerzeal.com
> >>> wrote:
> >>> Hey folks, the report is to be signed off today and I do not see it
> being
> >>> filled at http://wiki.apache.org/incubator/April2016.
> >>>
> >>> Appreciate if one of you could take care of this asap.
> >>>
> >>> Thanks!
> >>> Venkatesh
> >>>
> >>> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey<bu...@apache.org> wrote:
> >>>
> >>>> For those interested in posting feedback, the website jira is RYA-42
> >>>>
> >>>> On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu<ad...@usna.edu>
> >>> wrote:
> >>>>> I created a JIRA ticket for the website. If anyone has specific ideas
> >>> for
> >>>>> it, please fell free to mention/implement them. Otherwise I'll try to
> >>>>> use/customize the apache-website-template available at
> >>>>> https://github.com/apache/apache-website-template/ as soon as
> >>> possible,
> >>>> but
> >>>>> definitely before the next report is due
> >>>>>
> >>>>> Adina
> >>>>>
> >>>>> On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil<pu...@gmail.com>
> >>>> wrote:
> >>>>>> David and I tried to compile a process for creating a release -- we
> >>>> didn't
> >>>>>> get that far. The main thing blocking us at this point is the whole
> >>>>>> process for signing a release, no one we knew had a public key and
> >>> then
> >>>>>> David and I got lost/confused when trying to generate and register
> >>> one.
> >>>>>> All of this sounds borderline embarrassing since there is a lot of
> >>>>>> documentation out there but we didn't have time to fully digest it
> >> in
> >>>>>> time.
> >>>>>> I'm also not clear on what else we would need to do besides run mvn
> >>>>>> release, like compile release notes, etc. I'm sorry if there's a
> >> lot
> >>> of
> >>>>>> documentation exactly detailing what we need to do.
> >>>>>> Other than that, I think we've made a lot of progress as a community
> >>>> this
> >>>>>> past month. We've had a lot of new contributors, had a lot of new
> >>> bugs
> >>>>>> reported by new end users, and have closed out a lot of issues.
> >>>>>>
> >>>>>> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey<bu...@apache.org>
> >>> wrote:
> >>>>>>> Heya Rya!
> >>>>>>>
> >>>>>>> We're about 5-6 weeks from our next scheduled turn for the IPMC's
> >>>> board
> >>>>>>> report.
> >>>>>>>
> >>>>>>> How are folks doing? The project sounds a bit quiet to me, but I'm
> >>> not
> >>>>>>> sure how much of that is me being sure to look in the right
> >> places.
> >>>>>>> To Review, here are your self-identified three most important
> >>>> objectives:
> >>>>>>> 1. Populate the website for the project
> >>>>>>> 2. Expand the "how to" document to explain the ways new
> >>> contributors
> >>>>>> can
> >>>>>>> become involved in the project, so we increase the size of
> >> the
> >>>>>>> community.
> >>>>>>> 3. Become familiar with the release process and have a first
> >>>> release as
> >>>>>>> part of the Apache Foundation
> >>>>>>>
> >>>>>>> At least to me, numbers 1 and 3 seem like big barriers to getting
> >>> new
> >>>>>>> folks brought in. Anyone have a list of the blockers keeping us
> >> from
> >>>>>>> those two? I tried searching the jira for relevant tickets, but
> >>> didn't
> >>>>>>> find any.
> >>>>>>>
> >>>>>>> -Sean
> >>>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Dr. Adina Crainiceanu
> >>>>> http://www.usna.edu/Users/cs/adina/
> >>
> >>
> >> --
> >> Dr. Adina Crainiceanu
> >> http://www.usna.edu/Users/cs/adina/
> >>
> >
>
Re: Looking towards our next IPMC report
Posted by Josh Elser <jo...@gmail.com>.
+1 to Venkatesh's overall message (if I can put words in mouths): don't
get too hung up on "perfect the first time". Showing progress is much
more important.
Seetharam Venkatesh wrote:
> Thanks Adina, report looks good. There are quite a few low hanging issues
> that can be addressed quickly.
>
>> Become familiar with the release process and have a first release as part
> of the Apache Foundation
> I have done about 5 incubating releases and can help if someone can
> volunteer as an RM. This is not hard and its an easy win for a podling.
>
>> Expand the "how to" document to explain the ways new contributors can
> become involved in the project
> This can start simple and can be iterated. You can also look at what other
> incubating projects are doing.
>
>> We have a Rya "office hour" teleconference every other week
> Can you also please put this on the confluence wiki so its accessible.
>
> Thanks!
> Venkatesh
>
> On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu<ad...@usna.edu> wrote:
>
>> I submitted the report. Sorry for waiting till the last minute - I wanted
>> to have a website first :)
>>
>> Thank you,
>> Adina
>>
>> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh<
>> venkatesh@innerzeal.com
>>> wrote:
>>> Hey folks, the report is to be signed off today and I do not see it being
>>> filled at http://wiki.apache.org/incubator/April2016.
>>>
>>> Appreciate if one of you could take care of this asap.
>>>
>>> Thanks!
>>> Venkatesh
>>>
>>> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey<bu...@apache.org> wrote:
>>>
>>>> For those interested in posting feedback, the website jira is RYA-42
>>>>
>>>> On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu<ad...@usna.edu>
>>> wrote:
>>>>> I created a JIRA ticket for the website. If anyone has specific ideas
>>> for
>>>>> it, please fell free to mention/implement them. Otherwise I'll try to
>>>>> use/customize the apache-website-template available at
>>>>> https://github.com/apache/apache-website-template/ as soon as
>>> possible,
>>>> but
>>>>> definitely before the next report is due
>>>>>
>>>>> Adina
>>>>>
>>>>> On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil<pu...@gmail.com>
>>>> wrote:
>>>>>> David and I tried to compile a process for creating a release -- we
>>>> didn't
>>>>>> get that far. The main thing blocking us at this point is the whole
>>>>>> process for signing a release, no one we knew had a public key and
>>> then
>>>>>> David and I got lost/confused when trying to generate and register
>>> one.
>>>>>> All of this sounds borderline embarrassing since there is a lot of
>>>>>> documentation out there but we didn't have time to fully digest it
>> in
>>>>>> time.
>>>>>> I'm also not clear on what else we would need to do besides run mvn
>>>>>> release, like compile release notes, etc. I'm sorry if there's a
>> lot
>>> of
>>>>>> documentation exactly detailing what we need to do.
>>>>>> Other than that, I think we've made a lot of progress as a community
>>>> this
>>>>>> past month. We've had a lot of new contributors, had a lot of new
>>> bugs
>>>>>> reported by new end users, and have closed out a lot of issues.
>>>>>>
>>>>>> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey<bu...@apache.org>
>>> wrote:
>>>>>>> Heya Rya!
>>>>>>>
>>>>>>> We're about 5-6 weeks from our next scheduled turn for the IPMC's
>>>> board
>>>>>>> report.
>>>>>>>
>>>>>>> How are folks doing? The project sounds a bit quiet to me, but I'm
>>> not
>>>>>>> sure how much of that is me being sure to look in the right
>> places.
>>>>>>> To Review, here are your self-identified three most important
>>>> objectives:
>>>>>>> 1. Populate the website for the project
>>>>>>> 2. Expand the "how to" document to explain the ways new
>>> contributors
>>>>>> can
>>>>>>> become involved in the project, so we increase the size of
>> the
>>>>>>> community.
>>>>>>> 3. Become familiar with the release process and have a first
>>>> release as
>>>>>>> part of the Apache Foundation
>>>>>>>
>>>>>>> At least to me, numbers 1 and 3 seem like big barriers to getting
>>> new
>>>>>>> folks brought in. Anyone have a list of the blockers keeping us
>> from
>>>>>>> those two? I tried searching the jira for relevant tickets, but
>>> didn't
>>>>>>> find any.
>>>>>>>
>>>>>>> -Sean
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Dr. Adina Crainiceanu
>>>>> http://www.usna.edu/Users/cs/adina/
>>
>>
>> --
>> Dr. Adina Crainiceanu
>> http://www.usna.edu/Users/cs/adina/
>>
>
Re: Looking towards our next IPMC report
Posted by Seetharam Venkatesh <ve...@innerzeal.com>.
Thanks Adina, report looks good. There are quite a few low hanging issues
that can be addressed quickly.
> Become familiar with the release process and have a first release as part
of the Apache Foundation
I have done about 5 incubating releases and can help if someone can
volunteer as an RM. This is not hard and its an easy win for a podling.
> Expand the "how to" document to explain the ways new contributors can
become involved in the project
This can start simple and can be iterated. You can also look at what other
incubating projects are doing.
> We have a Rya "office hour" teleconference every other week
Can you also please put this on the confluence wiki so its accessible.
Thanks!
Venkatesh
On Wed, Apr 6, 2016 at 11:40 AM Adina Crainiceanu <ad...@usna.edu> wrote:
> I submitted the report. Sorry for waiting till the last minute - I wanted
> to have a website first :)
>
> Thank you,
> Adina
>
> On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh <
> venkatesh@innerzeal.com
> > wrote:
>
> > Hey folks, the report is to be signed off today and I do not see it being
> > filled at http://wiki.apache.org/incubator/April2016.
> >
> > Appreciate if one of you could take care of this asap.
> >
> > Thanks!
> > Venkatesh
> >
> > On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey <bu...@apache.org> wrote:
> >
> > > For those interested in posting feedback, the website jira is RYA-42
> > >
> > > On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu <ad...@usna.edu>
> > wrote:
> > > > I created a JIRA ticket for the website. If anyone has specific ideas
> > for
> > > > it, please fell free to mention/implement them. Otherwise I'll try to
> > > > use/customize the apache-website-template available at
> > > > https://github.com/apache/apache-website-template/ as soon as
> > possible,
> > > but
> > > > definitely before the next report is due
> > > >
> > > > Adina
> > > >
> > > > On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil <pu...@gmail.com>
> > > wrote:
> > > >
> > > >> David and I tried to compile a process for creating a release -- we
> > > didn't
> > > >> get that far. The main thing blocking us at this point is the whole
> > > >> process for signing a release, no one we knew had a public key and
> > then
> > > >> David and I got lost/confused when trying to generate and register
> > one.
> > > >> All of this sounds borderline embarrassing since there is a lot of
> > > >> documentation out there but we didn't have time to fully digest it
> in
> > > >> time.
> > > >> I'm also not clear on what else we would need to do besides run mvn
> > > >> release, like compile release notes, etc. I'm sorry if there's a
> lot
> > of
> > > >> documentation exactly detailing what we need to do.
> > > >> Other than that, I think we've made a lot of progress as a community
> > > this
> > > >> past month. We've had a lot of new contributors, had a lot of new
> > bugs
> > > >> reported by new end users, and have closed out a lot of issues.
> > > >>
> > > >> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bu...@apache.org>
> > wrote:
> > > >>
> > > >> > Heya Rya!
> > > >> >
> > > >> > We're about 5-6 weeks from our next scheduled turn for the IPMC's
> > > board
> > > >> > report.
> > > >> >
> > > >> > How are folks doing? The project sounds a bit quiet to me, but I'm
> > not
> > > >> > sure how much of that is me being sure to look in the right
> places.
> > > >> >
> > > >> > To Review, here are your self-identified three most important
> > > objectives:
> > > >> >
> > > >> > 1. Populate the website for the project
> > > >> > 2. Expand the "how to" document to explain the ways new
> > contributors
> > > >> can
> > > >> > become involved in the project, so we increase the size of
> the
> > > >> > community.
> > > >> > 3. Become familiar with the release process and have a first
> > > release as
> > > >> > part of the Apache Foundation
> > > >> >
> > > >> > At least to me, numbers 1 and 3 seem like big barriers to getting
> > new
> > > >> > folks brought in. Anyone have a list of the blockers keeping us
> from
> > > >> > those two? I tried searching the jira for relevant tickets, but
> > didn't
> > > >> > find any.
> > > >> >
> > > >> > -Sean
> > > >> >
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Dr. Adina Crainiceanu
> > > > http://www.usna.edu/Users/cs/adina/
> > >
> >
>
>
>
> --
> Dr. Adina Crainiceanu
> http://www.usna.edu/Users/cs/adina/
>
Re: Looking towards our next IPMC report
Posted by Adina Crainiceanu <ad...@usna.edu>.
I submitted the report. Sorry for waiting till the last minute - I wanted
to have a website first :)
Thank you,
Adina
On Wed, Apr 6, 2016 at 2:30 PM, Seetharam Venkatesh <venkatesh@innerzeal.com
> wrote:
> Hey folks, the report is to be signed off today and I do not see it being
> filled at http://wiki.apache.org/incubator/April2016.
>
> Appreciate if one of you could take care of this asap.
>
> Thanks!
> Venkatesh
>
> On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey <bu...@apache.org> wrote:
>
> > For those interested in posting feedback, the website jira is RYA-42
> >
> > On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu <ad...@usna.edu>
> wrote:
> > > I created a JIRA ticket for the website. If anyone has specific ideas
> for
> > > it, please fell free to mention/implement them. Otherwise I'll try to
> > > use/customize the apache-website-template available at
> > > https://github.com/apache/apache-website-template/ as soon as
> possible,
> > but
> > > definitely before the next report is due
> > >
> > > Adina
> > >
> > > On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil <pu...@gmail.com>
> > wrote:
> > >
> > >> David and I tried to compile a process for creating a release -- we
> > didn't
> > >> get that far. The main thing blocking us at this point is the whole
> > >> process for signing a release, no one we knew had a public key and
> then
> > >> David and I got lost/confused when trying to generate and register
> one.
> > >> All of this sounds borderline embarrassing since there is a lot of
> > >> documentation out there but we didn't have time to fully digest it in
> > >> time.
> > >> I'm also not clear on what else we would need to do besides run mvn
> > >> release, like compile release notes, etc. I'm sorry if there's a lot
> of
> > >> documentation exactly detailing what we need to do.
> > >> Other than that, I think we've made a lot of progress as a community
> > this
> > >> past month. We've had a lot of new contributors, had a lot of new
> bugs
> > >> reported by new end users, and have closed out a lot of issues.
> > >>
> > >> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bu...@apache.org>
> wrote:
> > >>
> > >> > Heya Rya!
> > >> >
> > >> > We're about 5-6 weeks from our next scheduled turn for the IPMC's
> > board
> > >> > report.
> > >> >
> > >> > How are folks doing? The project sounds a bit quiet to me, but I'm
> not
> > >> > sure how much of that is me being sure to look in the right places.
> > >> >
> > >> > To Review, here are your self-identified three most important
> > objectives:
> > >> >
> > >> > 1. Populate the website for the project
> > >> > 2. Expand the "how to" document to explain the ways new
> contributors
> > >> can
> > >> > become involved in the project, so we increase the size of the
> > >> > community.
> > >> > 3. Become familiar with the release process and have a first
> > release as
> > >> > part of the Apache Foundation
> > >> >
> > >> > At least to me, numbers 1 and 3 seem like big barriers to getting
> new
> > >> > folks brought in. Anyone have a list of the blockers keeping us from
> > >> > those two? I tried searching the jira for relevant tickets, but
> didn't
> > >> > find any.
> > >> >
> > >> > -Sean
> > >> >
> > >>
> > >
> > >
> > >
> > > --
> > > Dr. Adina Crainiceanu
> > > http://www.usna.edu/Users/cs/adina/
> >
>
--
Dr. Adina Crainiceanu
http://www.usna.edu/Users/cs/adina/
Re: Looking towards our next IPMC report
Posted by Seetharam Venkatesh <ve...@innerzeal.com>.
Hey folks, the report is to be signed off today and I do not see it being
filled at http://wiki.apache.org/incubator/April2016.
Appreciate if one of you could take care of this asap.
Thanks!
Venkatesh
On Wed, Feb 24, 2016 at 7:26 AM Sean Busbey <bu...@apache.org> wrote:
> For those interested in posting feedback, the website jira is RYA-42
>
> On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu <ad...@usna.edu> wrote:
> > I created a JIRA ticket for the website. If anyone has specific ideas for
> > it, please fell free to mention/implement them. Otherwise I'll try to
> > use/customize the apache-website-template available at
> > https://github.com/apache/apache-website-template/ as soon as possible,
> but
> > definitely before the next report is due
> >
> > Adina
> >
> > On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil <pu...@gmail.com>
> wrote:
> >
> >> David and I tried to compile a process for creating a release -- we
> didn't
> >> get that far. The main thing blocking us at this point is the whole
> >> process for signing a release, no one we knew had a public key and then
> >> David and I got lost/confused when trying to generate and register one.
> >> All of this sounds borderline embarrassing since there is a lot of
> >> documentation out there but we didn't have time to fully digest it in
> >> time.
> >> I'm also not clear on what else we would need to do besides run mvn
> >> release, like compile release notes, etc. I'm sorry if there's a lot of
> >> documentation exactly detailing what we need to do.
> >> Other than that, I think we've made a lot of progress as a community
> this
> >> past month. We've had a lot of new contributors, had a lot of new bugs
> >> reported by new end users, and have closed out a lot of issues.
> >>
> >> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bu...@apache.org> wrote:
> >>
> >> > Heya Rya!
> >> >
> >> > We're about 5-6 weeks from our next scheduled turn for the IPMC's
> board
> >> > report.
> >> >
> >> > How are folks doing? The project sounds a bit quiet to me, but I'm not
> >> > sure how much of that is me being sure to look in the right places.
> >> >
> >> > To Review, here are your self-identified three most important
> objectives:
> >> >
> >> > 1. Populate the website for the project
> >> > 2. Expand the "how to" document to explain the ways new contributors
> >> can
> >> > become involved in the project, so we increase the size of the
> >> > community.
> >> > 3. Become familiar with the release process and have a first
> release as
> >> > part of the Apache Foundation
> >> >
> >> > At least to me, numbers 1 and 3 seem like big barriers to getting new
> >> > folks brought in. Anyone have a list of the blockers keeping us from
> >> > those two? I tried searching the jira for relevant tickets, but didn't
> >> > find any.
> >> >
> >> > -Sean
> >> >
> >>
> >
> >
> >
> > --
> > Dr. Adina Crainiceanu
> > http://www.usna.edu/Users/cs/adina/
>
Re: Looking towards our next IPMC report
Posted by Sean Busbey <bu...@apache.org>.
For those interested in posting feedback, the website jira is RYA-42
On Wed, Feb 24, 2016 at 8:31 AM, Adina Crainiceanu <ad...@usna.edu> wrote:
> I created a JIRA ticket for the website. If anyone has specific ideas for
> it, please fell free to mention/implement them. Otherwise I'll try to
> use/customize the apache-website-template available at
> https://github.com/apache/apache-website-template/ as soon as possible, but
> definitely before the next report is due
>
> Adina
>
> On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil <pu...@gmail.com> wrote:
>
>> David and I tried to compile a process for creating a release -- we didn't
>> get that far. The main thing blocking us at this point is the whole
>> process for signing a release, no one we knew had a public key and then
>> David and I got lost/confused when trying to generate and register one.
>> All of this sounds borderline embarrassing since there is a lot of
>> documentation out there but we didn't have time to fully digest it in
>> time.
>> I'm also not clear on what else we would need to do besides run mvn
>> release, like compile release notes, etc. I'm sorry if there's a lot of
>> documentation exactly detailing what we need to do.
>> Other than that, I think we've made a lot of progress as a community this
>> past month. We've had a lot of new contributors, had a lot of new bugs
>> reported by new end users, and have closed out a lot of issues.
>>
>> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bu...@apache.org> wrote:
>>
>> > Heya Rya!
>> >
>> > We're about 5-6 weeks from our next scheduled turn for the IPMC's board
>> > report.
>> >
>> > How are folks doing? The project sounds a bit quiet to me, but I'm not
>> > sure how much of that is me being sure to look in the right places.
>> >
>> > To Review, here are your self-identified three most important objectives:
>> >
>> > 1. Populate the website for the project
>> > 2. Expand the "how to" document to explain the ways new contributors
>> can
>> > become involved in the project, so we increase the size of the
>> > community.
>> > 3. Become familiar with the release process and have a first release as
>> > part of the Apache Foundation
>> >
>> > At least to me, numbers 1 and 3 seem like big barriers to getting new
>> > folks brought in. Anyone have a list of the blockers keeping us from
>> > those two? I tried searching the jira for relevant tickets, but didn't
>> > find any.
>> >
>> > -Sean
>> >
>>
>
>
>
> --
> Dr. Adina Crainiceanu
> http://www.usna.edu/Users/cs/adina/
Re: Looking towards our next IPMC report
Posted by Adina Crainiceanu <ad...@usna.edu>.
I created a JIRA ticket for the website. If anyone has specific ideas for
it, please fell free to mention/implement them. Otherwise I'll try to
use/customize the apache-website-template available at
https://github.com/apache/apache-website-template/ as soon as possible, but
definitely before the next report is due
Adina
On Tue, Feb 23, 2016 at 10:01 PM, Puja Valiyil <pu...@gmail.com> wrote:
> David and I tried to compile a process for creating a release -- we didn't
> get that far. The main thing blocking us at this point is the whole
> process for signing a release, no one we knew had a public key and then
> David and I got lost/confused when trying to generate and register one.
> All of this sounds borderline embarrassing since there is a lot of
> documentation out there but we didn't have time to fully digest it in
> time.
> I'm also not clear on what else we would need to do besides run mvn
> release, like compile release notes, etc. I'm sorry if there's a lot of
> documentation exactly detailing what we need to do.
> Other than that, I think we've made a lot of progress as a community this
> past month. We've had a lot of new contributors, had a lot of new bugs
> reported by new end users, and have closed out a lot of issues.
>
> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bu...@apache.org> wrote:
>
> > Heya Rya!
> >
> > We're about 5-6 weeks from our next scheduled turn for the IPMC's board
> > report.
> >
> > How are folks doing? The project sounds a bit quiet to me, but I'm not
> > sure how much of that is me being sure to look in the right places.
> >
> > To Review, here are your self-identified three most important objectives:
> >
> > 1. Populate the website for the project
> > 2. Expand the "how to" document to explain the ways new contributors
> can
> > become involved in the project, so we increase the size of the
> > community.
> > 3. Become familiar with the release process and have a first release as
> > part of the Apache Foundation
> >
> > At least to me, numbers 1 and 3 seem like big barriers to getting new
> > folks brought in. Anyone have a list of the blockers keeping us from
> > those two? I tried searching the jira for relevant tickets, but didn't
> > find any.
> >
> > -Sean
> >
>
--
Dr. Adina Crainiceanu
http://www.usna.edu/Users/cs/adina/
Re: Looking towards our next IPMC report
Posted by Sean Busbey <bu...@apache.org>.
No need to be embarrassed, there is a wide variety of docs but that's partially
because things tend to vary by community and most of those docs aren't
authoritative.
There are a few things the ASF requires, some of which might be flexible while
you're in the incubator (largely depending on your mentors and the IPMC):
* Source artifact must exist
* Source artifact must correspond to some version control commit
* All artifact must adhere to LICENSE/NOTICE policies
* All artifacts must be signed and have checksums (atleast md5, preferably also
sha*)
* [VOTE] thread must be called on dev@ with pointers to the above and a period
of >= 72hrs
Since you're incubating, after you have the above you then need a [VOTE] by the
IPMC, which is done on general@incubator.
Some pointers that might help:
* The Incubator guide to releasing while incubating:
http://incubator.apache.org/guides/releasemanagement.html
* I recently wrote a draft release guide for Apache Yetus that covers what tools
you'll need and the process step-by-step:
https://issues.apache.org/jira/browse/YETUS-226
There are some differences; namely Yetus is a TLP so it has its own staging
and release areas and doesn't need an IPMC vote. Most importantly, it includes
pointers to ASF guides on generating and publishing GPG keys. If it doesn't
give enough guidance I'd be interested in feedback.
On Tue, Feb 23, 2016 at 9:01 PM, Puja Valiyil <pu...@gmail.com> wrote:
> David and I tried to compile a process for creating a release -- we didn't
> get that far. The main thing blocking us at this point is the whole
> process for signing a release, no one we knew had a public key and then
> David and I got lost/confused when trying to generate and register one.
> All of this sounds borderline embarrassing since there is a lot of
> documentation out there but we didn't have time to fully digest it in
> time.
> I'm also not clear on what else we would need to do besides run mvn
> release, like compile release notes, etc. I'm sorry if there's a lot of
> documentation exactly detailing what we need to do.
> Other than that, I think we've made a lot of progress as a community this
> past month. We've had a lot of new contributors, had a lot of new bugs
> reported by new end users, and have closed out a lot of issues.
>
> On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bu...@apache.org> wrote:
>
>> Heya Rya!
>>
>> We're about 5-6 weeks from our next scheduled turn for the IPMC's board
>> report.
>>
>> How are folks doing? The project sounds a bit quiet to me, but I'm not
>> sure how much of that is me being sure to look in the right places.
>>
>> To Review, here are your self-identified three most important objectives:
>>
>> 1. Populate the website for the project
>> 2. Expand the "how to" document to explain the ways new contributors can
>> become involved in the project, so we increase the size of the
>> community.
>> 3. Become familiar with the release process and have a first release as
>> part of the Apache Foundation
>>
>> At least to me, numbers 1 and 3 seem like big barriers to getting new
>> folks brought in. Anyone have a list of the blockers keeping us from
>> those two? I tried searching the jira for relevant tickets, but didn't
>> find any.
>>
>> -Sean
>>
Re: Looking towards our next IPMC report
Posted by Puja Valiyil <pu...@gmail.com>.
David and I tried to compile a process for creating a release -- we didn't
get that far. The main thing blocking us at this point is the whole
process for signing a release, no one we knew had a public key and then
David and I got lost/confused when trying to generate and register one.
All of this sounds borderline embarrassing since there is a lot of
documentation out there but we didn't have time to fully digest it in
time.
I'm also not clear on what else we would need to do besides run mvn
release, like compile release notes, etc. I'm sorry if there's a lot of
documentation exactly detailing what we need to do.
Other than that, I think we've made a lot of progress as a community this
past month. We've had a lot of new contributors, had a lot of new bugs
reported by new end users, and have closed out a lot of issues.
On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bu...@apache.org> wrote:
> Heya Rya!
>
> We're about 5-6 weeks from our next scheduled turn for the IPMC's board
> report.
>
> How are folks doing? The project sounds a bit quiet to me, but I'm not
> sure how much of that is me being sure to look in the right places.
>
> To Review, here are your self-identified three most important objectives:
>
> 1. Populate the website for the project
> 2. Expand the "how to" document to explain the ways new contributors can
> become involved in the project, so we increase the size of the
> community.
> 3. Become familiar with the release process and have a first release as
> part of the Apache Foundation
>
> At least to me, numbers 1 and 3 seem like big barriers to getting new
> folks brought in. Anyone have a list of the blockers keeping us from
> those two? I tried searching the jira for relevant tickets, but didn't
> find any.
>
> -Sean
>