Re: OpenStack Upstream Institute

[Roman Shaposhnik]

I've been thinking of this style of even a lot recently.

Basically an ASF bootcamp for students and the like who want to break
into open source but don't quite know how.

Have a day and a place with a lot of existing ASF committers/PMC
around and an objective of having your first real commit accepted into
a real ASF project.

The commit itself could be anything -- the point is to break that ice
and just feel like it is doable.

Thanks,
Roman.

On Thu, Aug 8, 2019 at 9:51 AM Rich Bowen  wrote:
>
> I just attended a great session about the OpenStack Upstream Institute,
> and I would love to see us do a similar thing. Perhaps starting at
> ApacheCon 2020, but possibly as stand-alone roadshow type events. Just
> something to consider, as a way to build skilled contributor communities.
>
> Basic idea: One day (or up to 2, depending) on how to contribute to
> $project. They do intro "how to do open source" content, and then drill
> down to project-specific content later in the day.
>
> By the end of the day, students will have pushed one patch, with good
> commit message, to some project. But much of the content is more about
> culture than specific project or technical details.
>
> Perhaps this is something that the Training PMC should be doing instead
> - but I think all of those people are here, too.
>
> I've pasted my full notes from the meeting below, for those that want
> more context.
>
> Resources:
>
> Upstream institute wiki page:
> https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute
>
> Upstream training guide:  https://docs.openstack.org/upstream-training/
>
> OpenStack Contributor guide: https://docs.openstack.org/contributors/
>
> OpenStack community page:  https://www.openstack.org/community/
>
> Full Notes:
>
> Ildiko and Kendall presented today about the OpenStack Upstream Institute.
>
> OUI is an in-person training about how to contribute to OpenStack, as
> well as being general open source advocates. Open design, development,
> community, and source.
>
> First training was 5 years ago before OpenStack Summit.
>
> Training is to help newcomers get over the hurdles of contributions.
> Training has evolved over the years based on lessons learned.
>
> Training is 1 or 1.5 days long. Lots of Q and exercises.
>
> Covers governance, release cycle, how teams are structures, how doc/code
> development is going. Account setup is part of the day. Walk them
> through sending their first patch and navigating the review process. How
> to revise changes. Git basics. How you communicate with the community.
> How to test your changes. Running and configuring devstack.
>
> Training is very interactive, to keep people engaged. Lots of exercises
> to ensure that the attendees grasped the material and can act on it.
>
> Have project mentors attend, so that they can recommend “low hanging”
> issues that the trainees can address.
>
> This is *not* training about how to use/administer OpenStack itself.
>
> No criteria for people to join the training. All levels of experience
> are represented, and the day has to be crafted around that, so sometimes
> it takes all available time, and sometimes it’s done much faster.
>
> There is a lot of culture that is passed along to the participants,
> which includes open source norms. These are also informed by the 4 Opens.
>
> People involved in the training include board members, PTLs (project
> technical leads), mentors, current developers. Representation from all
> of the various major sections of the community. Largely a community
> effort, rather than just pushed by the Foundation.
>
> All of the slides/text are translated into multiple languages so that
> they can be presented to local audiences more effectively.
>
> Many of the projects host project-specific onboarding. Culture, system
> setup, other technical details.
>
> There is also a mentoring program which attendees can participate in if
> they need more help.
>
> Training is the day before OpenStack Summit/Open Infrastructure Summit.
> Also at regional OpenStack Days, Open Infra Days, which are smaller
> events all around the world.
>
> Encourage people to keep in touch with one another after the training.
> This is especially useful with regional trainings, so that people are in
> the same region/timezone, and have a local project community.
>
> When space/time isn’t available at an event, run office hours where
> people can drop by and ask questions, get help.
>
> Local events, a couple dozen attendees. At major international events,
> more like 60 - 80 attendees.
>
> Resources listed in the etherpad:
>
> Upstream institute wiki page:
> https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute
> Upstream training guide:  https://docs.openstack.org/upstream-training/
> OpenStack Contributor guide: https://docs.openstack.org/contributors/
> OpenStack community page:  https://www.openstack.org/community/
> May be other things :)
>
> Started with lecture format, and evolved into the current, more-hands on

Please add Apache Ignite Logo to RedBubble

[Dmitriy Pavlov]

Dear Community Developers,

Could you please add Apache Ignite Logo to RedBubble?

Logo http://apache.org/logos/#ignite

Sincerely,
Dmitriy Pavlov

[jira] [Commented] (COMDEV-315) Fix Russian translation for Apache Brochure

[Dmitriy Pavlov (JIRA)]

[ 
https://issues.apache.org/jira/browse/COMDEV-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903343#comment-16903343
 ] 

Dmitriy Pavlov commented on COMDEV-315:
---

[~sebb], yes, and discussion was stopped since marketing was going to update 
statistics first.

I'm not sure issue can be completed now.

> Fix Russian translation for Apache Brochure
> ---
>
> Key: COMDEV-315
> URL: https://issues.apache.org/jira/browse/COMDEV-315
> Project: Community Development
>  Issue Type: Bug
>  Components: Comdev
>Reporter: Dmitriy Pavlov
>Assignee: Roman Shaposhnik
>Priority: Major
>
> The Russian translation has a very messed up font kerning.
> Related discussion:
> https://lists.apache.org/thread.html/c926035ccb50282b9769770c8276c8c1f172ee6c68b32b37d6381cf7@%3Cdev.community.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

OpenStack Upstream Institute

[Rich Bowen]

I just attended a great session about the OpenStack Upstream Institute, 
and I would love to see us do a similar thing. Perhaps starting at 
ApacheCon 2020, but possibly as stand-alone roadshow type events. Just 
something to consider, as a way to build skilled contributor communities.


Basic idea: One day (or up to 2, depending) on how to contribute to 
$project. They do intro "how to do open source" content, and then drill 
down to project-specific content later in the day.


By the end of the day, students will have pushed one patch, with good 
commit message, to some project. But much of the content is more about 
culture than specific project or technical details.


Perhaps this is something that the Training PMC should be doing instead 
- but I think all of those people are here, too.


I've pasted my full notes from the meeting below, for those that want 
more context.


Resources:

Upstream institute wiki page: 
https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute


Upstream training guide:  https://docs.openstack.org/upstream-training/

OpenStack Contributor guide: https://docs.openstack.org/contributors/

OpenStack community page:  https://www.openstack.org/community/

Full Notes:

Ildiko and Kendall presented today about the OpenStack Upstream Institute.

OUI is an in-person training about how to contribute to OpenStack, as 
well as being general open source advocates. Open design, development, 
community, and source.


First training was 5 years ago before OpenStack Summit.

Training is to help newcomers get over the hurdles of contributions. 
Training has evolved over the years based on lessons learned.


Training is 1 or 1.5 days long. Lots of Q and exercises.

Covers governance, release cycle, how teams are structures, how doc/code 
development is going. Account setup is part of the day. Walk them 
through sending their first patch and navigating the review process. How 
to revise changes. Git basics. How you communicate with the community. 
How to test your changes. Running and configuring devstack.


Training is very interactive, to keep people engaged. Lots of exercises 
to ensure that the attendees grasped the material and can act on it.


Have project mentors attend, so that they can recommend “low hanging” 
issues that the trainees can address.


This is *not* training about how to use/administer OpenStack itself.

No criteria for people to join the training. All levels of experience 
are represented, and the day has to be crafted around that, so sometimes 
it takes all available time, and sometimes it’s done much faster.


There is a lot of culture that is passed along to the participants, 
which includes open source norms. These are also informed by the 4 Opens.


People involved in the training include board members, PTLs (project 
technical leads), mentors, current developers. Representation from all 
of the various major sections of the community. Largely a community 
effort, rather than just pushed by the Foundation.


All of the slides/text are translated into multiple languages so that 
they can be presented to local audiences more effectively.


Many of the projects host project-specific onboarding. Culture, system 
setup, other technical details.


There is also a mentoring program which attendees can participate in if 
they need more help.


Training is the day before OpenStack Summit/Open Infrastructure Summit. 
Also at regional OpenStack Days, Open Infra Days, which are smaller 
events all around the world.


Encourage people to keep in touch with one another after the training. 
This is especially useful with regional trainings, so that people are in 
the same region/timezone, and have a local project community.


When space/time isn’t available at an event, run office hours where 
people can drop by and ask questions, get help.


Local events, a couple dozen attendees. At major international events, 
more like 60 - 80 attendees.


Resources listed in the etherpad:

Upstream institute wiki page: 
https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute

Upstream training guide:  https://docs.openstack.org/upstream-training/
OpenStack Contributor guide: https://docs.openstack.org/contributors/
OpenStack community page:  https://www.openstack.org/community/
May be other things :)

Started with lecture format, and evolved into the current, more-hands on 
format, over the years based on attendee feedback and attention span.


Writing exercises is very challenging.

Quizzes at the beginning of the second day to ensure that they retained 
everything from the first day. Review the answers afterwards.


Attendee surveys afterwards to improve for the next time.

Success metrics: Do you advocate at your company? What have you done? 
Have you pushed a patch since then?


Track contributor activity after the training, to see if they got it. 
(Be sure to register with the same email/github that you use to 
contribute, so that this reflects actual activity.)


There’s at 

Jena logo on RedBubble

[Claude Warren]

One more for the pile

Can we get jena logo on RedBubble plz.

thx

-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [Lazy Consensus] Changing the default reporter tool

[Jan Høydahl]

Happy to help somewhere. If slack counts is something you see useful to track, 
I'd be happy to whip up a Kibble scanner plugin for Slack, if that makes sense?

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

> 8. aug. 2019 kl. 15:16 skrev Rich Bowen :
> 
> If I might make a plug ... two, in fact.
> 
> 1) The Kibble project, which provides these statistics, is a warm welcoming 
> place, if anyone is looking for a way to contribute to an exciting project.
> 
> 2) reporter.a.o lives in the community.apache.org svn repo, and welcomes 
> patches.
> 
> As both Kibble PMC chair, and a ComDev PMC member, I am often concerned by 
> the degree to which many of our project conversations are people asking for 
> stuff, and then Daniel doing it. Yes, Daniel does awesome work, but 
> bus-factor-1 project make me very, very squidgy. Both for sustainability of 
> the project when Daniel burns out, and for the misperception that this 
> service is somehow a function of Infra and should have an SLA.
> 
> So ... all that to say, we really would love to see more people tinkering 
> with this code.
> 
> -- 
> Rich Bowen - rbo...@rcbowen.com
> http://rcbowen.com/
> @rbowen
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 

Re: [Lazy Consensus] Changing the default reporter tool

[Rich Bowen]

If I might make a plug ... two, in fact.

1) The Kibble project, which provides these statistics, is a warm 
welcoming place, if anyone is looking for a way to contribute to an 
exciting project.


2) reporter.a.o lives in the community.apache.org svn repo, and welcomes 
patches.


As both Kibble PMC chair, and a ComDev PMC member, I am often concerned 
by the degree to which many of our project conversations are people 
asking for stuff, and then Daniel doing it. Yes, Daniel does awesome 
work, but bus-factor-1 project make me very, very squidgy. Both for 
sustainability of the project when Daniel burns out, and for the 
misperception that this service is somehow a function of Infra and 
should have an SLA.


So ... all that to say, we really would love to see more people 
tinkering with this code.


--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [Lazy Consensus] Changing the default reporter tool

[Jan Høydahl]

Just one more suggestion - perhaps Slack metrics would make sense as well for 
the community health of a project?

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

> 6. aug. 2019 kl. 18:58 skrev Daniel Gruno :
> 
> On 8/6/19 6:48 PM, Joan Touzet wrote:
>> On 2019-08-06 12:47, Daniel Gruno wrote:
>>> On 8/6/19 6:43 PM, Jan Høydahl wrote:
> 6. aug. 2019 kl. 17:35 skrev Daniel Gruno :
>> Another question - I don't see mailing list stats for the list
>> solr-u...@lucene.apache.org ,
>> what is the logic behind what lists to show and not?
>> The solr-user@ list has 1403 mails last 3 months
>> https://lists.apache.org/list.html?solr-u...@lucene.apache.org:lte=3M:
>> 
>> 
> 
> It shows lists where there is a change to what happened in the
> previous quarter, that is, if traffic went up or down by more than a
> few percent.
> We could opt to display all lists on the statistics page, and keep
> the editor as just showing the ones with significant changes.
 
 The Lucene project has several lists that not active due to historic
 reasons, such as c-commits@, ruby-dev@, solr-commits@, java-commits@
 and c-dev@ and more.
 
 The old reporter lists all of these and that is just noise. What if we
 show all lists with some significant traffic, and filter out those
 with 0 (or very few) mails?
 The % change is btw not a very reliable metric for low-volume lists
 such as our gene...@lucene.apache.org, it will probably be tagged as
 increasing/decreasing every single quarter (10-30 email).
 
>>> 
>>> Consider it done. All lists with fewer than 10 emails in
>>> present/previous quarter (depending on the trend) are filtered out and
>>> the rest are now all shown :) on the statistics page, that is.
>> Request to never filter out dev@. If dev@ is really that quiet...we (PMC
>> members, or the Board) should know about it.
> 
> I've added a special "if dev@" rule to always show the stats for that list.
> 
>> -Joan
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@community.apache.org 
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org 
> 
> For additional commands, e-mail: dev-h...@community.apache.org 
> 

Please add Sling logo to RedBubble + stickers for ApacheCon

[Robert Munteanu]

Hi,

Please add the Sling logo to RedBubble

  https://www.apache.org/logos/#sling

I will be present at ApacheCon EU, so some stickers for that conference
would be great.

Thanks,

Robert


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

AW: How to add swag to the redbubble shop?

[Julian Feinauer]

Hi Chris,

Thanks for your initiative. Of course you can also count on me when a second 
hand is needed!

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: How to add swag to the redbubble shop?
Von: Christofer Dutz
An: dev@community.apache.org
Cc:

Hi all,

I'm currently reading all of these "please add project x logo to redbubble". 
The plc4x project would also like to do this, but I expect more than just 
adding a logo being necessary for that.

I would volunteer to do that for the plc4x project.

Chris


Holen Sie sich Outlook für Android