[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipse.org-architecture-council] [Bug 250315] Improve Attendance tracking for AC Calls
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=250315
Product/Component: Community / Architecture Council
Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gunnar@xxxxxxxxxxxxxxx
--- Comment #11 from Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> 2008-10-10 02:57:29 -0400 ---
(In reply to comment #9)
> Have you ever searched for such content in wiki.
Good point, the wiki search is horrible. Just compared a search for
"architecture council call" using the wiki search[1] and Google site search[2].
The wiki leads to nowhere. The first hit on Google leads to the Architecture
council's page with the call schedule.
[1]
http://wiki.eclipse.org/Special:Search?search=architecture+council+call&go.x=0&go.y=0&go=Go
[2]
http://www.google.de/search?hl=de&q=architecture+council+call+site%3Awiki.eclipse.org&btnG=Google-Suche&meta=
> [...] I don't like
> gaterhering private data, but it should not block our processes.
Not sure what private data you mean. Eclipse is Open Source. Our names, our AC
membership info, the call schedule, everything is already in the wiki and
public available. The Google Bot should have it already.
(In reply to comment #0)
I think it's a matter of trust. Everybody who joined a call and cares can add
himself to the attendee list on the wiki page *after* the call. As Martin said
in the call, participation in calls is not the most important thing. A lot more
can be achieved asynchronous on mailing lists, bugzilla and other asynchronous
channels.
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
