infrastructure/blender-org
5
4
Fork 1
Code Issues 16 Pull Requests Projects Releases Wiki Activity

add what mailing list new developers need to use.(wiki.blender.org) #37500

New Issue
Closed
opened 2013-11-17 16:50:38 +01:00 by Scott Petrovic · 5 comments
Scott Petrovic commented 2013-11-17 16:50:38 +01:00
Copy Link

http://wiki.blender.org/index.php/Dev:Doc/New_Developer_Info

Provide single mailing list for new developers/volunteers to reach out to on the wiki. Currently, the new developer contact page says "See the Contact and Get Involved pages for more information about these."

For new users, there is a lot to take in with all of the information and documentation that is out there. All of the reference links are making it more difficult to figure out where to go. There are more projects than there are mailing lists also. Things like UI don't have mailing lists. It can be confusing knowing where to go.

Action

  1. It would be better to change "See the Contact and Get Involved pages for more information about these." to something like "Sign up for the bf-committers@blender.org mailing list and talk with developers about getting involved further. Provide a link to the list.

thoughts?

Scott

http://wiki.blender.org/index.php/Dev:Doc/New_Developer_Info Provide single mailing list for new developers/volunteers to reach out to on the wiki. Currently, the new developer contact page says "See the Contact and Get Involved pages for more information about these." For new users, there is a lot to take in with all of the information and documentation that is out there. All of the reference links are making it more difficult to figure out where to go. There are more projects than there are mailing lists also. Things like UI don't have mailing lists. It can be confusing knowing where to go. Action 1. It would be better to change "See the Contact and Get Involved pages for more information about these." to something like "Sign up for the bf-committers@blender.org mailing list and talk with developers about getting involved further. Provide a link to the list. thoughts? Scott
Scott Petrovic commented 2013-11-17 16:50:38 +01:00
Author
Copy Link

Changed status to: 'Open'

Changed status to: 'Open'
Scott Petrovic commented 2013-11-17 16:50:38 +01:00
Author
Copy Link

Added subscriber: @scottyp

Added subscriber: @scottyp
Brecht Van Lommel commented 2013-11-18 06:19:07 +01:00
Owner
Copy Link

Added subscriber: @brecht

Added subscriber: @brecht
Brecht Van Lommel commented 2013-11-18 06:19:07 +01:00
Owner
Copy Link

I changed the text to this now:

Most communication happens on mailing lists, irc chat and the bug and patch trackers. See the Contact for more information. When in doubt and no particular channel seems to match your question, mail the bf-committers mailing list and you will get an answer there or get redirected to the right channel.

Generally if people want to get involved e.g. working on cycles or writing addons, it's best to ask on the special interest list, so I don't want to give the impression that everyone should aways mail bf-committers first.

I changed the text to this now: > Most communication happens on mailing lists, irc chat and the bug and patch trackers. See the Contact for more information. When in doubt and no particular channel seems to match your question, mail the bf-committers mailing list and you will get an answer there or get redirected to the right channel. Generally if people want to get involved e.g. working on cycles or writing addons, it's best to ask on the special interest list, so I don't want to give the impression that everyone should aways mail bf-committers first.
Brecht Van Lommel commented 2013-11-18 06:19:15 +01:00
Owner
Copy Link

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Brecht Van Lommel self-assigned this 2013-11-18 06:19:15 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
legacy module
Rendering & Cycles

  
legacy module
User Interface

  
legacy project
Cycles

  
legacy project
Documentation

  
legacy project
Infrastructure: blender.org

  
legacy project
Infrastructure: Blender Web Assets

  
legacy project
Infrastructure: Websites

  
legacy project
User Interface

  
Priority
High

  
Priority
Low

  
Priority
Normal

  
Priority
Unbreak Now!

  
Status
Archived

  
Status
Confirmed

  
Status
Duplicate

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Known Issue

  
Type
Report

  
Type
To Do

No Label
legacy module
Rendering & Cycles
legacy module
User Interface
legacy project
Cycles
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Blender Web Assets
legacy project
Infrastructure: Websites
legacy project
User Interface
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Brecht Van Lommel
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-org#37500
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?