Changes between Initial Version and Version 1 of MapGuideRfc58


Ignore:
Timestamp:
Jan 14, 2009, 1:45:40 PM (13 years ago)
Author:
tomfukushima
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc58

    v1 v1  
     1= !MapGuide RFC 58 - Setting up a "Donate to Builds" process for the build infrastructure =
     2
     3This page contains an change request (RFC) for the !MapGuide Open Source project.
     4More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     5
     6
     7== Status ==
     8
     9||RFC Template Version||(1.0)||
     10||Submission Date||TBD (Date/Time submitted)||
     11||Last Modified|| Tom Fukushima [[Timestamp]]||
     12||Author|| Tom Fukushima and Trevor Wekel ||
     13||RFC Status||draft (proposed, frozen for vote, adopted, retracted, or rejected)||
     14||Implementation Status|| pending (under development, completed)||
     15||Proposed Milestone||2.1||
     16||Assigned PSC guide(s)|| Tom Fukushima||
     17||'''Voting History'''||(vote date)||
     18||+1|| ||
     19||+0|| ||
     20||-0|| ||
     21||-1|| ||
     22||no vote|| ||
     23
     24== Overview ==
     25
     26This RFC describes the !PayPal setup and processes that we will use to allow community members to donate funds to the build infrastructure; and how reports will be provided.
     27
     28== Motivation ==
     29
     30MGOS needs to put together a build environment in order to make things more transparent and to be in control.  An important part of this is having build infrastructure that is available to the developers on the internet. Trevor has offered some machines which can be set up to fulfill our needs. However, there are hosting, hardware, and software costs that need to be covered. With this in mind, we feel that a !PayPal account should be a viable solution to allow community members to make contributions, no matter what the size, so that we can sustain the builds.
     31
     32
     33== Proposed Solution ==
     34
     35TBD
     36
     37This is a more detailed description of the actual changes desired.  The contents of this section will vary based on the target of the RFC, be it a technical change, website change, or process change.  For example, for a technical change, items such as files, XML schema changes, and API chances would be identified.  For a process change, the new process would be laid out in detail.  For a website change, the files affected would be listed.
     38
     39== Implications ==
     40
     41This section allows discussion of the repercussions of the change, such as whether there will be any breakage in backwards compatibility, if documentation will need to be updated, etc.
     42
     43== Test Plan ==
     44
     45How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
     46
     47== Funding/Resources ==
     48
     49This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.