Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

83%
+8 −0
Q&A Voluntariness vs. Responsibility, which of them should be considered as a priority for the community team?

The Codidact community team have accepted to be the staff and run the community. So, in my opinion, if Codidact is an aspiring platform, one may expect that they work as paid staff do. Am I right?...

posted 3y ago by manassehkatz‭  ·  last activity 3y ago by manassehkatz‭

Answer
#1: Initial revision by user avatar manassehkatz‭ · 2020-09-29T01:44:21Z (over 3 years ago)
> The Codidact community team have accepted to be the staff and run the community. So, in my opinion, if Codidact is an aspiring platform, one may expect that they work as paid staff do.
> 
> Am I right?

I see two very different issues of:

### Productivity

As noted by others, the volunteers have limited time for this (or any other) volunteer project, so unless they feel a particular feature is important enough to spend the time on, it won't get done. That is **normal** for a volunteer project.  This has a major impact on feature requests. 

### Professionalism

This covers two areas:

* Quality of Code

As with any open source project, quality of code will vary a lot. But, within certain limits, adding more people to the project will increase code quality as there are more people reviewing code and helping to improve it. The truth is, commercial code varies quite a bit in quality too - most people just never see it.

* Interactions within the Project and with the Public

While hard to enforce - not so easy to kick someone out for misbehaving when anyone can volunteer and no money is involved - this is most definitely a goal in Codidact. Volunteers are expected to treat each other with respect and to treat the end users (i.e., people actively making use of Codidact but not contributing to the code or other core parts of the project) with respect. This is, of course, a two-way street. If users are not themselves respectful of the Codidact volunteers (developers and moderators) then they may get an (unfortunate) bit of disrespect back, though part of the goal of moderation is to minimize such issues and, using tools such as closing questions and removing user privileges, to keep the overall conversation polite, respectful and, by certain definitions, *professional.*

Back to the original question: If the issue is "volunteers should treat users and user requests professionally" (i.e., with respect, politeness, etc.) then I agree. If the issue is "volunteers should handle all feature requests quickly simply because I **know** they are important and will improve the system" - no, that is not a reasonable expectation for an all-volunteer project.