[jira] [Commented] (COMDEV-326) Committer invite template omits PMC role details

[Rich Bowen (Jira)]

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

Rich Bowen commented on COMDEV-326:
---

[https://github.com/apache/www-site/pull/421] adds link to the template.

> Committer invite template omits PMC role details
> 
>
> Key: COMDEV-326
> URL: https://issues.apache.org/jira/browse/COMDEV-326
> Project: Community Development
>  Issue Type: Bug
>  Components: Website
> Environment: 
> https://community.apache.org/newcommitter.html#committer-invite-template
>Reporter: Sebb
>Priority: Major
>
> The committer invite template [1] is not very clear on the distinction 
> between an invitation as a committer, and invitation as a committer + PMC 
> member.
> In particular, it describes the role of the committer, but largely ignores 
> the PMC role.
> As a result, I have seen at least one acceptance reply that said "I accept to 
> become a committer" [2] - leaving unstated whether or not they agree to 
> become a PMC member.
> I think any template needs to make very clear what is involved in the PMC 
> role, and also that the invitee has 3 choices:
> - decline both invites
> - accept the committer invite and decline the PMC invite
> - accept both committer invite and PMC invite
> [1] https://community.apache.org/newcommitter.html#committer-invite-template
> [2] 
> https://lists.apache.org/thread.html/796c4b3e8c0f191add39c7d1b6cc154a5e316910df8120db1151c739@%3Cprivate.jackrabbit.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (COMDEV-550) Replacement for Red Bubble (merch site)

[Rich Bowen (Jira)]

Rich Bowen created COMDEV-550:
-

 Summary: Replacement for Red Bubble (merch site)
 Key: COMDEV-550
 URL: https://issues.apache.org/jira/browse/COMDEV-550
 Project: Community Development
  Issue Type: Task
  Components: Comdev
Reporter: Rich Bowen


The RedBubble site has been shut down. We need to research and implement 
replacement where people can order stickers and other branded merch for ASF 
projects, primarily for individual purchase by fans, but also for bulk orders 
for events and other purposes.

Context: 
[https://cwiki.apache.org/confluence/display/COMDEV/How+To%3A+Add+Project+Logos+to+Redbubble+Store]

If you want to work on this, please speak up on dev@community so that you can 
connect with those who have done this work in the past, to avoid known 
obstacles.

Subtasks include:
 * Identify projects that had content listed on the old site and ensure that 
they get onto the new site
 * Contact other projects to make them aware of this service, and get their 
logos there
 * Work with Treasurer to figure out if we can earn income from a site like 
this, or if we need to sell at cost (tax considerations, etc)

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: ASF installation of Apache Answer

[Gavin McDonald]

On Sun, Oct 27, 2024 at 4:02 PM Piotr P. Karwasz
 wrote:
>
> Hi all,
>
> At CoCEU 2024, we talked about installing an Apache Answer[1] instance
> common to all Apache Software Foundation. Is there some progress in this
> direction or did the suggestion never reach any official channel?

https://issues.apache.org/jira/browse/INFRA-25866

tl;dr Infra created the Answer project a VM for exactly this purpose.

You now need to contact the Answer project to found out how things
are progressing. The VM and the service itself is to be maintained as
a 'project' service.

HTH

Gav...

>
> Personally I would really like to have an ASF equivalent of
> StackOverflow Collectives[2]. Collectives is a premium service for
> communities provided by StackOverflow that adds the following features
> to SO:
>
> 1. It recognizes the merit that each participant has in its own
> community, e.g. in our case it could clearly mark the answers provided
> by a PMC member or committer.
>
> 2. It provides statistics about each community, so we can also know how
> many experts in ASF technologies are there, even those that never
> reported a bug or contributed to the project.
>
> Unfortunately, SO Collectives is exclusively a commercial service. About
> two years ago I reached out to SO, to ask if they can open a Collective
> for Apache Logging Services, so if the ASF is interested, I could share
> in private the exact figures I received at that time and some contacts
> in SO.
>
> As far as I have seen, Apache Answer could be an answer (pun intended)
> to the needs above.
>
> Piotr
>
> [1] https://answer.apache.org/
>
> [2] https://stackoverflow.com/collectives
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>


-- 

Gavin McDonald -
Systems Administrator, ASF Infrastructure Team
V.P Travel Assistance Committee

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

[jira] [Created] (COMDEV-549) Template "where is everything" template file for projects

[Rich Bowen (Jira)]

Rich Bowen created COMDEV-549:
-

 Summary: Template "where is everything" template file for projects
 Key: COMDEV-549
 URL: https://issues.apache.org/jira/browse/COMDEV-549
 Project: Community Development
  Issue Type: Task
  Components: Comdev
Reporter: Rich Bowen


Create recommended template "where is everything" for projects which answers 
the basic questions that people have about a project. This includes:
 * What is it? (What does it do? What problem does it solve? Who is it for?)
 * Mission statement (Aspirational statement that says what's in scope and what 
it wants to be when it grows up)
 * Where is the code?
 * Where is the *website* source?
 * Where is the documentation?
 * Where do we communicate?
 * Who are we? (List (active?) PMC members)
 * What is the primary programming language?

Bonus tasks:
 * Recommend a "standard" URL where this information should be displayed, so 
that [project].apache.org/about can be relied on to provide this information
 * Fill-in form that produces this content in a standard order, in a variety of 
markup formats



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: Should HelpWanted be shut down?

[Rich Bowen]

FWIW, I’ve opened https://github.com/apache/httpd-site/pull/15 to remove this 
from the httpd page.

—Rich

> On Oct 26, 2024, at 8:07 AM, Rich Bowen  wrote:
> 
> 
> On Fri, Oct 25, 2024, 4:38 AM sebb  > wrote:
>> 
>> 
>> Do we need to let projects who have used this service know?
>> 
>> I think there are a couple of projects that directly link to the
>> service (e.g. https://httpd.apache.org/, bottom of page)
> 
> 
> It is worth noting that the *newest* entry listed there is 6 years old.
> 
> I was almost certain that I removed that feature from the website years ago. 
> Either I misremembered or someone reverted that. Weird.

— 
Rich Bowen
rbo...@rcbowen.com

ASF installation of Apache Answer

[Piotr P. Karwasz]

Hi all,

At CoCEU 2024, we talked about installing an Apache Answer[1] instance 
common to all Apache Software Foundation. Is there some progress in this 
direction or did the suggestion never reach any official channel?


Personally I would really like to have an ASF equivalent of 
StackOverflow Collectives[2]. Collectives is a premium service for 
communities provided by StackOverflow that adds the following features 
to SO:


1. It recognizes the merit that each participant has in its own 
community, e.g. in our case it could clearly mark the answers provided 
by a PMC member or committer.


2. It provides statistics about each community, so we can also know how 
many experts in ASF technologies are there, even those that never 
reported a bug or contributed to the project.


Unfortunately, SO Collectives is exclusively a commercial service. About 
two years ago I reached out to SO, to ask if they can open a Collective 
for Apache Logging Services, so if the ASF is interested, I could share 
in private the exact figures I received at that time and some contacts 
in SO.


As far as I have seen, Apache Answer could be an answer (pun intended) 
to the needs above.


Piotr

[1] https://answer.apache.org/

[2] https://stackoverflow.com/collectives


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

[jira] [Resolved] (COMDEV-230) Reorg sample presentations by topic

[Rich Bowen (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rich Bowen resolved COMDEV-230.
---
Resolution: Fixed

Done. Long, long ago.

> Reorg sample presentations by topic
> ---
>
> Key: COMDEV-230
> URL: https://issues.apache.org/jira/browse/COMDEV-230
> Project: Community Development
>  Issue Type: Task
>  Components: Website
>Reporter: Rich Bowen
>Priority: Major
>
> https://community.apache.org/speakers/slides.html lists slides/presentations 
> that have been given in the past.
> While this is useful, the organization of the page is wrong for the use case. 
> In particular, we want people to be able to obtain information about 
> particular topics - the Apache Way, the Incubator, and so on. Ordering the 
> page by name puts the emphasis the wrong place.
> So, two steps:
> 1) reorder the page by topic rather than by personal name.
> 2) Work towards recommended starter presentations for important topics (eg, 
> Apache Way) that have standard talking points, and things that must/should be 
> covered.
> It's possible that #2 should be a separate ticket - per topic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (COMDEV-541) Need an apache.org email address for a content producer

[Rich Bowen (Jira)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rich Bowen resolved COMDEV-541.
---
Resolution: Resolved

This was for an event that is now past.

> Need an apache.org email address for a content producer
> ---
>
> Key: COMDEV-541
> URL: https://issues.apache.org/jira/browse/COMDEV-541
> Project: Community Development
>  Issue Type: Improvement
>  Components: Comdev
>Reporter: Claude Warren
>Priority: Major
>
> Teyza needs an apache.org email address so that her emails about Community 
> over Code EU look official.
>  
> her external email is [te...@sg.com.mx|mailto:te...@sg.com.mx]
> we would like to get [te...@apache.org|mailto:te...@apache.org] if possible.
>  
> Thank you
> Claude



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: Reorg of new committer advice

[Jarodney Marcus]

Can you say this so that I can understand

On Sunday, October 27, 2024, Rich Bowen  wrote:

> Hey, folks,
>
> https://github.com/apache/comdev-site/pull/187
>
> This is a proposed rewrite/reorg of the New Committer advice, as well as
> some tweaks to the various email templates, several of which were either
> wrong, or grossly outdated.
>
> It also creates a top-level templates/ directory where we’ll put
> (surprise!) templates, which will make it easier to find those files, and
> easier to enhance specific templates in one place, and reference them from
> multiple other places.
>
> I would appreciate some eyes on this, especially the accuracy and
> thoroughness of the committer-welcome.txt template, particularly with
> regard to the svn vs git advice — although I do encourage each project to
> create their own version of that welcome template, since each project has
> their own nuances.
>
> (I’m planning to do the same kind of edit to newpmcmember.md later this
> week, but probably not today.)
>
> —Rich
>
>
> —
> Rich Bowen
> rbo...@rcbowen.com
>
>
>
>
>

Reorg of new committer advice

[Rich Bowen]

Hey, folks,

https://github.com/apache/comdev-site/pull/187

This is a proposed rewrite/reorg of the New Committer advice, as well as some 
tweaks to the various email templates, several of which were either wrong, or 
grossly outdated.

It also creates a top-level templates/ directory where we’ll put (surprise!) 
templates, which will make it easier to find those files, and easier to enhance 
specific templates in one place, and reference them from multiple other places.

I would appreciate some eyes on this, especially the accuracy and thoroughness 
of the committer-welcome.txt template, particularly with regard to the svn vs 
git advice — although I do encourage each project to create their own version 
of that welcome template, since each project has their own nuances.

(I’m planning to do the same kind of edit to newpmcmember.md later this week, 
but probably not today.)

—Rich 


— 
Rich Bowen
rbo...@rcbowen.com