Jump to: navigation, search

Difference between revisions of "Architecture Council/Ask the AC"

(Questions about Eclipse)
Line 13: Line 13:
 
= Moderator =
 
= Moderator =
  
= Questions to Ask =
+
= Questions to Ask (FAQ type) =
== Questions about the AC (FAQ type) ==
+
== About the AC ==
 
* '''What would happen if the AC went away?'''
 
* '''What would happen if the AC went away?'''
 
** A: New projects would lose their mentors, who can help them get acquainted to the Eclipse Ecosystem. Other AC tasks would likely be picked up by other bodies such as the Planning Council or the Committer Reps, but a useful body for information interchange would likely be missing.
 
** A: New projects would lose their mentors, who can help them get acquainted to the Eclipse Ecosystem. Other AC tasks would likely be picked up by other bodies such as the Planning Council or the Committer Reps, but a useful body for information interchange would likely be missing.
Line 34: Line 34:
 
** A: An initial response can be expected within 1-2 work days, an actual resolution of an issue depends on how hard the issue is. Some things can be solved by E-Mail / bugzilla interactions only, while others require agreement in meeting or consulting with other bodies. Most things should be resolved over 2 meetings (i.e. 2 months) at most, so please inquire back on your bug if you don't get a satisfactory answer by then.
 
** A: An initial response can be expected within 1-2 work days, an actual resolution of an issue depends on how hard the issue is. Some things can be solved by E-Mail / bugzilla interactions only, while others require agreement in meeting or consulting with other bodies. Most things should be resolved over 2 meetings (i.e. 2 months) at most, so please inquire back on your bug if you don't get a satisfactory answer by then.
  
== Questions about Mentorship ==
+
== Mentorship ==
 
* '''What are the most frequently asked questions to you as a mentor?'''
 
* '''What are the most frequently asked questions to you as a mentor?'''
 
** A: How do other projects (perform builds, organize their bugs, organize their website); what is the standard/expected way of (doing X).
 
** A: How do other projects (perform builds, organize their bugs, organize their website); what is the standard/expected way of (doing X).
 +
* '''What do you see as the key to success getting Community Contributions for your project?'''
 +
** A: Caring for bug reports and questions, then asking for contributions and caring for them. Contributions come out of bug reports or questions (assuming that the project is actually being used already).
 
* '''How much time do you have for coding, compared to other tasks?'''
 
* '''How much time do you have for coding, compared to other tasks?'''
 
** A: Always too little :-)
 
** A: Always too little :-)
  
== Questions about Process ==
+
== Development Process ==
* '''What do you see as the key to success getting Community Contributions for your project?'''
+
** A: Caring for bug reports and questions, then asking for contributions and caring for them. Contributions come out of bug reports or questions (assuming that the project is actually being used already).
+
 
* '''What is the most problematic violation of IP policies that you've come across so far, and how do you avoid IP violations in your projects?'''
 
* '''What is the most problematic violation of IP policies that you've come across so far, and how do you avoid IP violations in your projects?'''
 
** A: Copy and paste because 3rd party sources are so easily available in Eclipse. Constant reminders for committers.
 
** A: Copy and paste because 3rd party sources are so easily available in Eclipse. Constant reminders for committers.
Line 48: Line 48:
 
** A: Make the process your own: the process is there for everybody's good, and having to do some documentation etc pays back in terms of community development. By changing the mind to see the process as your friend rather than foe, you'll find it much less of a burden. Then, look for mentor's advice and tooling where you still find it cumbersome.
 
** A: Make the process your own: the process is there for everybody's good, and having to do some documentation etc pays back in terms of community development. By changing the mind to see the process as your friend rather than foe, you'll find it much less of a burden. Then, look for mentor's advice and tooling where you still find it cumbersome.
  
== Questions about Eclipse ==  
+
== Eclipse ==  
 
* '''How do you remain informed about what's going on at Eclipse?'''
 
* '''How do you remain informed about what's going on at Eclipse?'''
 
** A: Planet Eclipse and the monthly AC meetings :-)
 
** A: Planet Eclipse and the monthly AC meetings :-)

Revision as of 09:18, 13 January 2009

EclipseCon Entry

This page is for collecting ideas for the "Ask the AC" panel at EclipseCon 2009.

Participants

Moderator

Questions to Ask (FAQ type)

About the AC

  • What would happen if the AC went away?
    • A: New projects would lose their mentors, who can help them get acquainted to the Eclipse Ecosystem. Other AC tasks would likely be picked up by other bodies such as the Planning Council or the Committer Reps, but a useful body for information interchange would likely be missing.
  • What power does the AC really have?
    • A: First of all, the power of the high technical reputation that the AC members have in their respective bodies; but also the power that the combined technical expertise of the entire Ecosystem has when interacting with the EMO, the Board or the Projects. We do not, however, have direct power over any budget.
  • How does one avail oneself of the august wisdom that is the AC? (Open a bugzilla?)
    • A: Yes, by filing a bug against the AC via the Architecture Council homepage or by putting the eclipse.org-architecture-council@eclipse.org bugzilla user on CC of an existing bug.
  • Who can do the availing? Is it just the PMC's? Or can a muggle ask questions too?
    • A: Anybody can ask, as long as the AC can handle the bandwidth.
  • What are appropriate AC questions?
    • A: See the list of questions that has been asked before (available from the Architecture Council wiki homepage). Asking for a mentor is the most common question, but questions of process, culture, netiquette, infrastructure, or programming patterns can be asked too - especially if they have a nature spanning multiple or all Eclipse projects.
  • Where can I find the accumulated decisions of the AC?
    • A: On the Architecture Council Wiki, which has links to the list of resolved Bugzilla's, meeting notes and wiki pages.
  • If the AC says something, does that mean it is gospel, or is the AC just advisory?
    • A: Well the gospel position is taken, and the AC cannot physically force anybody to do anything. But given that the most influencial members including Mike Milinkovich are on the AC, the AC can say things with authority that's better not ignored.
  • Who/what is the official mouthpiece of the AC?
    • A: Any delegate that the AC names, in most cases it will be the Chair of the AC (currently Martin Oberhuber).
  • How fast does the AC turn around questions?
    • A: An initial response can be expected within 1-2 work days, an actual resolution of an issue depends on how hard the issue is. Some things can be solved by E-Mail / bugzilla interactions only, while others require agreement in meeting or consulting with other bodies. Most things should be resolved over 2 meetings (i.e. 2 months) at most, so please inquire back on your bug if you don't get a satisfactory answer by then.

Mentorship

  • What are the most frequently asked questions to you as a mentor?
    • A: How do other projects (perform builds, organize their bugs, organize their website); what is the standard/expected way of (doing X).
  • What do you see as the key to success getting Community Contributions for your project?
    • A: Caring for bug reports and questions, then asking for contributions and caring for them. Contributions come out of bug reports or questions (assuming that the project is actually being used already).
  • How much time do you have for coding, compared to other tasks?
    • A: Always too little :-)

Development Process

  • What is the most problematic violation of IP policies that you've come across so far, and how do you avoid IP violations in your projects?
    • A: Copy and paste because 3rd party sources are so easily available in Eclipse. Constant reminders for committers.
  • Following the Development Process takes so much time! How do I fulfill the Process with the least effort?
    • A: Make the process your own: the process is there for everybody's good, and having to do some documentation etc pays back in terms of community development. By changing the mind to see the process as your friend rather than foe, you'll find it much less of a burden. Then, look for mentor's advice and tooling where you still find it cumbersome.

Eclipse

  • How do you remain informed about what's going on at Eclipse?
    • A: Planet Eclipse and the monthly AC meetings :-)
  • What do you see as the biggest challenge to Eclipse in the next 10 years?
    • A: The burden of backward compatibility for a HUGE ecosystem while having to remain at the forefront of innovation
    • A: Scaling up to more and more integrated technologies while remaining slick
  • What do you see as the biggest chance for Eclipse today?
    • A: As Equinox and the EPL get adopted in other communities, more alignment and integration. The e4 project has large potential as well.
  • Who really shot JFK?