<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Jason,<br>
<br>
I updated the PSC page and also granted you the Documentation Developer
role so you can make changes to the website. As for our little
conflict, do you think you could maybe outline the process you feel we
should use so we can understand it better? Maybe that will allow us to
come up with a happy little compromise in the middle.<br>
<br>
Thanks,<br>
Bob<br>
<br>
<br>
Jason Birch wrote:
<blockquote
cite="mid8E468917B01800408B91984428BE03DD0385F7F9@starfish.nanaimo.ca"
type="cite">
<pre wrap="">Hey, I agree. It's an argument in my favour :)
Bob, can I get content developer (or contributor, or whatever is needed for www changes) rights to the MapGuide project? I'd like to update the PSC page to add Haris.
Jason
________________________________
From: Haris Kurtagic
Sent: Sat 2006-10-28 10:36 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:psc@mapguide.osgeo.org">psc@mapguide.osgeo.org</a>
Subject: RE: [mapguide-psc] RFC process...
This is my first time involvement in open source and don't know much about RFC's, so I hope I am on topic.
I would like to point that I think that every person comment counts, no meter if user/developer/..
So, I think this RFC's templates needs to be easy understandable and that every one can express opinion no metter on skills.
It is not good if they are too techincal and pre-finished so non-developers got "affraid" to contribute to them.
I suppose this is not new and presumably we all agree on this. Anyhow I wanted to express my opinion.
Haris
________________________________
From: Jason Birch [<a class="moz-txt-link-freetext" href="mailto:Jason.Birch@nanaimo.ca">mailto:Jason.Birch@nanaimo.ca</a>]
Sent: Saturday, October 28, 2006 7:17 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:psc@mapguide.osgeo.org">psc@mapguide.osgeo.org</a>
Subject: RE: [mapguide-psc] RFC process...
Does working group sound better? :)
I think that the website, documentation, etc will be an area where non-developers will really be able to contribute, and the split between coding/presentation is clear enough (at least in my fuzzy mind) that splitting the work between coders/documentors would be reasonable. As an aside, I think that these two roles would need to be distinct in LDAP. Anyway, this is a while down the road and will come up again.
I don't buy that a solution a developer has thought through and even coded themselves is necessesarily the best solution for the project. By nature a single individual, or even a single organisation, does not have the breadth of experience or understanding of the problem realm to create a solution that is the best fit for our entire user base. We need to ensure that the project does not turn into a Frankenstein's monster of solutions that have been built in isolation. The problem is that the investment (time and emotion) in fait-accomplis solutions is such that it is difficult to shift their path once they are presented unless there is a severe defect.
I concede that a lot of the existing development will likely come as pre-canned solutions because of where this project is starting from, and that in some cases it will be desirable to accept contributions to the code base that have been developed in isolation, but I really want to stress that by default we should have open development starting at the conceptualisation phase.
Jason
________________________________
From: Robert Bray [<a class="moz-txt-link-freetext" href="mailto:rbray@robertbray.net">mailto:rbray@robertbray.net</a>]
Sent: Sat 2006-10-28 12:00 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:psc@mapguide.osgeo.org">psc@mapguide.osgeo.org</a>
Subject: Re: [mapguide-psc] RFC process...
Jason,
Personally I would like to avoid subcommittees, mainly because of the
pain OSGeo is feeling now due to fragmentation. Whether we need an RFC
for the web site is a different debate, maybe / maybe not. It really
depends on the scope of the change.
To address your core concern though, I expect a mix of RFCs. Some will
start with lots of discussion on the dev list and evolve into a fully
baked RFC. Others may come pre-baked, because the developer has already
thought it through pretty thoroughly (and maybe even has a prototype
running). It really depends highly on the author and what is being
proposed. The key is to welcome active discussion of ideas on the dev
list. Also remember that an RFC is a living document up until the time
it is voted on and approved. It can start with just an idea and no
implementation detail. We should make that clear on the how to create an
RFC page (hmm guess we need one of those).
Does that clarify or confuse the issue more?
Bob
Jason Birch wrote:
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/index.php/MapGuide_RFC_Template">http://wiki.osgeo.org/index.php/MapGuide_RFC_Template</a>
Do we really want the RFC process to apply to the web site? Maybe for major overhauls, but personally I think that this kind of thing could be better dealt with informally, perhaps by a web site subcommittee.
Also, I'm a bit scared of an RFC process that appears to expect the presentation of a well-thought-out canned solution, which is then subject to debate on the DEV list. I think that we should be encouraging an informal process where a problem/solution pair (or just the problem) is put forward to the DEV list/channel as a rough WIKI page, and is then debated and polished into a form where it can be submitted as an RFC.
This kind of process gives us better solutions, and ensures that the original submitter only needs to do a limited amount of work before starting the discussion, reducing the emotional attachment to a particular solution.
Jason
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>