ulc-devs team mailing list archive

["pablo.a.saavedra@xxxxxxxxx" <pablo.a.saavedra@xxxxxxxxx>]

>
>
> blueprints
>> ----------
>>
>> Before coding all details, we should probably make a round of design
>> proposals and discussion. We need to decide on the categories and
>> filters we want to support in the lens. We also need to decide on the
>> actions we want to be able to perform on contacts. (For details on the
>> lens architecture, see [2].)
>>
>
> I assume we are discussing the features on this list. What about
> documenting what we come up with? Should we create a wiki or something like
> this? I'm really new to all this, so don't exactly know what would be best.
>

We have the wiki  option or use Launchpad's blueprints

>
>
>> version control
>> ---------------
>>
>> When using launchpad, bzr is set. bzr allows for a centralized
>> (SVN-like) and a decentralized (git-like) approach. So we could either
>> set up a group branch and commit all to it, or we could work on personal
>> branches and merge them into master once they are ready for inclusion.
>>
>> I personally like the decentralized approach better. So I would suggest
>> to create a team branch as trunk, but do the work on personal branches
>> and merge them into trunk from time to time.
>>
>
> +1 on the decentralized approach. Again, something which I've never done
> before, so I have some questions ;)
> Where do we keep the local branches? Does it local literally mean, that we
> keep them only on our hard disk and once we are done with our changes, we
> commit them to the main branch? Or do we keep them somewhere on launchpad
> (probably in a branch related to our launchpad account, e.g.
> ~launchpad_id/+junk/branchname)?
>

We create personal branches on Launchpad were we push changes to. When the
code is ready, it's merged to the main branch.


Regards