[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Debconf-team] website presence meeting: crunch time.



Hi all

PyConZA is over which means it's website time.

I don't think we'll find a time for everyone to attend the meeting, so
we need to be clear on the meeting objectives and make this as
cooperative as possible. Bear this in mind and put your thoughts in
the titanpad [1] accordingly so that your voice is heard. Ideally,
then, it won't matter who attends, and hey, then we can even settle
this over email!

May I suggest Wednesday 18:00 UTC just because I see no other
alternative. Please feel free to suggest another day/time.

* The main meeting objective:
Decide on which system(s) are being developed as contenders for the
DC16 website. (If we feel we can decide to only go with wafer, that
would be *amazing*)
* Secondary objective:
Decide on a deadline for the contenders to show their stuff so we can
make a final decision. Winner takes all. Current suggestion is 31
October.

Then, to get as much discussion done before then, on the titanpad [1],
I suggest:

* Can we get an idea for what is in the running, and who is driving it?
Systems intended to show convincing argument by deadline, and lead
person driving it:
wafer (hodgestar)
odoo? (madduck?)
(edrz?)
(Ganneff?)
Drupal (gwolf)?
(Modify as appropriate on the titanpad, not in the email thread)

* Then I put the advantages and disadvantages for each 'contender'.
The way this is written feels very battle-like, which is not (really)
intended. If you have another way of summarising this, please go ahead
(a table in a wiki?) The point is that at the meeting I don't want to
go through all of this, it should be clear by then.

Everyone involved/interested should know by the start of the meeting:
1) What systems are going to be developed to a convincing point by the
deadline (possibly end of October), and who will be driving each
process
2) What are the general feelings for the advantages and disadvantages of each.
This meeting is NOT for people to argue for systems that they won't be
helping to develop. That you can do before the meeting, on the
titanpad.

In the event that we deal with this in a short time, there's a few
other agenda points like Visual Design we can focus on, which is much
more fun.

regards
B

[1] - https://titanpad.com/443gTylF6p

Reply to: