?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
pgpioEAS068cP.pgp
Description: PGP signature
