Hi everyone,

As usual things have slipped a bit. However, I am currently on holiday and at 
PyCon UK.

So, one thing that I can do here is suggest a sprint tomorrow to work on the 
ideas and possibly create more code for the django based core bloodhound and 
maybe more depending on what people are interested in doing here.

One pitfall in this is that, certainly for large code contributions, we would 
need ICLAs. For the purpose of the sprint, it will probably be best to use a 
fork of a repo so to avoid hindering progress on the day and see if I can 
convince people to go through the ICLA process.

So, any thoughts from anyone?

Meanwhile, there are probably some tasks that we could do with performing that 
are a bit overdue:

 * there appeared to be good support for developing our experimental bloodhound 
based on django with git for source control. This should probably just be done 
soon.
 * we could do with checking on the main project page and check that it is up 
to any required standards for apache projects
 * for the experimental branch (whether on a git repo or in svn) we need to 
make sure the licensing is up to date and corrected to correctly adress 
whatever is actually there.
 * reason about the appropriate content of the core project (at the moment 
things like the manage.py and various other items are committed to the branch 
and there may be better ways to structure the project - that also leads to 
questions about documenting general project setup)

I will try to raise tickets around these things soon.

Cheers,
    Gary

Reply via email to