[ANN] Contribution needed - bugs.erlang.org

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[ANN] Contribution needed - bugs.erlang.org

Bruce Yinhe-2
Hi 

Since the launch of bugs.erlang.org, many issues have been reported by the community. You might have noticed that some issues are labelled as "Contribution Needed":


This means that the OTP team has looked at the issue and would like help from the community. You are encouraged to contribute to Erlang by joining the discussion and/or helping solving these issues. 

Contribute to Erlang/OTP:

1. Look for issues labelled as "Contribution Needed".
2. Discuss in the issue comment.
3. Agree on a solution/implementation.
4. Submit the contribution as a pull request on Github.
5. An OTP team member reviews the implementation and merges the change. 

You are also encouraged to contribute by joining the discussion on issues which are "Open". 

Best regards

Bruce Yinhe
Community Manager
Industrial Erlang User Group
+46 72 311 43 89

--
Visit our Erlang community site ErlangCentral.org | @ErlangCentral | Industrial Erlang User Group

_______________________________________________
erlang-bugs mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-bugs
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] Contribution needed - bugs.erlang.org

Michael Santos-2
On Thu, Mar 31, 2016 at 11:05:28AM +0200, Bruce Yinhe wrote:

> Hi
>
> Since the launch of bugs.erlang.org, many issues have been reported by the
> community. You might have noticed that some issues are labelled as
> *"Contribution
> Needed"*:
>
> http://bugs.erlang.org/issues/?jql=status%3D%22Contribution%20Needed%22
>
>
> This means that the OTP team has looked at the issue and would like help
> from the community. You are encouraged to contribute to Erlang by joining
> the discussion and/or helping solving these issues.
>
> Contribute to Erlang/OTP:
>
> 1. Look for issues labelled as "Contribution Needed".
> 2. Discuss in the issue comment.
> 3. Agree on a solution/implementation.
> 4. Submit the contribution as a pull request on Github.
> 5. An OTP team member reviews the implementation and merges the change.
>
>
> You are also encouraged to contribute by joining the discussion on issues
> which are "Open".

Why does logging in with your github account require full access (write
access) to your github account personal details?

Is there a way of monitoring for new issues? For example, could new
issues be forwarded to the old erlang-bugs mail list?

>
> Best regards
>
> *Bruce Yinhe*
> Community Manager
> Industrial Erlang User Group
> +46 72 311 43 89
> [hidden email]
>
> _______________________________________________
> erlang-bugs mailing list
> [hidden email]
> http://erlang.org/mailman/listinfo/erlang-bugs

_______________________________________________
erlang-bugs mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-bugs
Loading...