1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
Some [[tschwinge]] comments regarding your proposal. Which is very good, if I
may say so again! :-)
Of course, everyone is invited to contribute here!
I want to give the following methodology a try, instead of only having
email/IRC discussions -- for the latter are again and again showing a tendency
to be dumped and deposited into their respective archives, and be forgotten
there. Of course, email/IRC discussions have their usefulness too, so we're
not going to replace them totally. For example, for conducting discussions
with a bunch of people (who may not even be following these pages here), email
(or, as applicable, the even more interactive IRC) will still be the medium of
choice. (And then, the executive summary should be posted here, or
incorporated into your proposal.)
Also, if you disagree with this suggested procedure right away, or at some
later point begin to feel that this thing doesn't work out, or simply takes too
much time (I don't think so: writing emails takes time, too), just say so, and
we can reconsider.
Of course, as this wiki is a passive medium rather than an active one as IRC
and email are, it is fine to send notices like: *I have updated the wiki page,
please have a look*.
One idea is that your proposal evolves alongside with the ongoing work, and
represents (in more or less detail) what has been done and what will be done.
Also, we can hopefully use parts of it for documentation purposes, or as
recipes for similar work (enabling other programming languages on the Hurd, for
example).
For this, I suggest the following procedure: as applicable, you can either
address any comments in here (for example, if they're wrong :-), or if they
require further discussion; think: *email discussion*), or you can address them
directly in your propoal and remove the comments from here at the same time
(think: *bug fix*).
Generally, you can assume that for things I didn't comment on (within some
reasonable timeframe/upon asking me again) that I'm fine with them. Otherwise,
I might say: *I don't like this as is, but I'll need more time to think about
it.*
There is also a possibility that parts of your proposal will be split off; in
cases where we think they're valuable to follow, but not at this time. (As you
know, your proposal is not really a trivial one, so it may just be too much for
one person's summer.) Such bits could be moved to [[open_issues]] pages,
either new ones or existing ones, as applicable.
# GSoC Site Discussion
* Discussion items from
<http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/jkoenig/1>
should be copied here:
* technical bits (obviously);
* also the *why do we want Java bindings* reasoning;
* CLISP findings should also be documented somewhere permanently.
* We should probaby open up a *languages for Hurd* section on the web
pages ([[!taglink open_issue_documentation]]).
|
