← Back to team overview

acmeattic-devel team mailing list archive

Re: [AcmeAttic] Design doc: Plan of action

 

Like what Aditya suggested on another thread, I agree that we should try to
get off the ground soon.
For that initiative, I think we need to get the following things straight
and in a consensus.


   - Solidify revision, encryption schemes for the first alpha release. Eg:
   I vote for skipping Snapshotting, provisions for revision merging and
   similar performance features. We would already need a lot of infrastructure
   set up to get to Release 1.
   - Programming tools: Eg. I vote for tools like Protocol buffers, Python
   Twisted framework, pycrypto library (More on the Wiki [1])
   - Protocol followed by client-server interaction (including messages).

Its the time to start creating some Blueprints on Launchpad, and attaching
clean write-ups of the proposals on the Wiki.

On Mon, Jul 5, 2010 at 4:14 AM, Aditya M <aditya87@xxxxxxxxx> wrote:

> On Sun, Jul 4, 2010 at 21:37, Karthik Swaminathan Nagaraj <
> nkarthiks@xxxxxxxxx> wrote:
>
>> I've drafted out a draft of the feature list at
>> http://www.nkarthiks.info/acmeattic/index.php?title=Feature_List
>> Take a look at it, and feel free to move things around.
>> It definitely needs more information. Maybe it can be populated as we
>> discuss, with implementation details.
>>
>
> We'll edit that. At the same time let's also think on how to plan the
> features schedule for various releases. I've written a vague list with PK's
> help here:
> http://www.nkarthiks.info/acmeattic/index.php?title=Release_Schedule
>
> --
> Aditya Manthramurthy
>
>


-- 
Karthik

Follow ups