2014-03-12 2:11 GMT+01:00 Brian Anderson bander...@mozilla.com:
[snip]
-
Many changes, including bug fixes and documentation improvements can be
implemented and reviewed via the normal GitHub pull request workflow.
Some changes though are substantial, and we ask that these be put
Rather than discuss this here, let's start dogfooding:
https://github.com/rust-lang/rfcs/pull/2
On Wed, Mar 12, 2014 at 3:54 AM, Flaper87 flape...@gmail.com wrote:
2014-03-12 2:11 GMT+01:00 Brian Anderson bander...@mozilla.com:
[snip]
-
Many changes, including bug fixes and
On 12/03/2014 01:11, Brian Anderson wrote:
* Fork the RFC repohttp://github.com/rust-lang/rfcs
* Copy `-template.md` to `active/-my-feature.md` (where
'my-feature' is descriptive. don't assign an RFC number yet).
* Fill in the RFC
* Submit a pull request. The pull request is the time to
Should the mailing list be involved in this process, as a way to get more
people discussing RFCs?
I'm using Github's watch feature on the RFC repo so that I am
automatically emailed whenever a new PR pops up or a discussion occurs.
These emails then get filtered to a Rust RFCs folder for easier
On 03/12/2014 12:54 AM, Flaper87 wrote:
2014-03-12 2:11 GMT+01:00 Brian Anderson bander...@mozilla.com
mailto:bander...@mozilla.com:
[snip]
-
Many changes, including bug fixes and documentation improvements can
be implemented and reviewed via the normal GitHub pull request
On 03/12/2014 03:42 AM, Simon Sapin wrote:
On 12/03/2014 01:11, Brian Anderson wrote:
* Fork the RFC repohttp://github.com/rust-lang/rfcs
* Copy `-template.md` to `active/-my-feature.md` (where
'my-feature' is descriptive. don't assign an RFC number yet).
* Fill in the RFC
* Submit a
We should also use tags: `Rejected` / `Approved`
I'm specifically trying to avoid those words :) 'approved' is stronger than
I want, because an approved RFC still may not get merged into the language,
and being 'rejected' is unfun.
XMPP uses the XEP process, which has decent names for
Hey, Rusties.
The freewheeling way that we add new features to Rust has been good for
early development, but for Rust to become a mature platform we need to
develop some more self-discipline when it comes to changing the system.
So this is a proposed modification to our current RFC process to
