I am currently working on the code but I will be adjusting the project wiki appropriately tonight.(already 10pm here) Also, to my knowledge, the deadline for the mid-term evaluations is on August 2.
- İlim 2013/7/29 Vinod Kone <[email protected]> > Thanks for update Ilim! > > I agree that adjusting the project's GSOC roadmap is a good idea. And I'm > with Jan on making "Authentication" the focus of this project. Lets knock > that down before the end of this summer. If we magically have more time > left, we will think of other fun stuff to hack on. > > Ilim, can you update the wiki with the updated roadmap? It would be great > to have it before mid-term evaluations (by July 31st?). > > And to reiterate, don't hesitate to mail your questions/concerns to the > mailing list. We are here to help. > > > > On Sun, Jul 28, 2013 at 7:50 PM, Jan Schaumann <[email protected]>wrote: > >> ?lim U?ur <[email protected]> wrote: >> >> > I updated the wiki page which was set up to present the scope and >> contents >> > of the Google Summer of Code project for adding security and >> authentication >> > support to Mesos. >> >> Thanks for fleshing this out a bit more. Looking forward to further >> updates here! >> >> > I realize that it still does not cover the whole material(i.e. a >> complete >> > schedule) but as the mid-term evaluations are starting tomorrow, I am >> > afraid any further updates on the wiki page will have to wait a few more >> > days as I am dealing with the project itself. However, after the >> deadline >> > for the mid-term evaluations, I will add any currently absent content >> and >> > will keep the page up to date from then on. >> >> Good! For GSoC projects, this kind of documentation is really >> important, as it allows others to view the good work you do and help you >> meet (or refine) your goals. The midterm evaluation in particular is >> not meant to judge your project by the number of lines of code you >> produced -- having a solid project outline is essential prior to being >> able to make true progress. >> >> > Here is a link to it: >> > >> https://cwiki.apache.org/confluence/display/MESOS/Authentication%2C+Authorization+and+Security+support >> >> As we're nearing the midterm, I think it'd be wise for us to ensure that >> the project as the correct scope and can be completed as desired. >> >> I'd like to suggest to adjust the scope of the project to only add >> 'Authentication' support. Authorization is, generally, a rather >> separate problem from authentication, and we don't want to confuse the >> two. >> >> Similarly, the phrase 'add security' here is not very useful, as that is >> rather all-encompassing. Focusing on authentication only will allow us >> to more tightly define the project outcomes and measurable progress -- >> which, again, goes back to actually having the milestones we wish to >> accomplish written down and communicated. >> >> What I'd like to see on the wiki page would be: >> >> - a defined, measurable end-of-project outcome (for example, "mesos >> clients and masters are able to authenticate one another via >> auth-mechanism X") >> - a break down of this outcome into smaller milestones >> - a calendar with dates by which these milestones should be completed >> - a 'current status' one-liner, updated regularly so that interested >> parties can see where we are >> - if you have a project blog, please add a link (if you don't have a >> blog, consider starting one -- even short updates outlining what you >> may be working on right now, what's blocking you etc. all can help >> tremendously) >> >> More frequent updates to these lists would probably also be welcome. >> This is not to "keep taps" on your work, but to allow the rest of the >> community to help you. >> >> -Jan >> > > -- > You received this message because you are subscribed to the Google Groups > "Twitter GSOC" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > >
