Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

collaboration - How to let people collaborate on my open source project? -


a while ago started open-source project, me meant (until now) pushed source code public repository (mercurial on google code). though, i've received requests other people collaborate on project. having never collaborated on open-source project before, i'm not sure how proceed:

  • do give them access repository can push changes? if push don't can roll , if on nerves can revoke access repository.
  • do tell them send in patches (via issue tracker) , apply ones , revoke ones don't?

now:

  • i don't want lose ownership of project. it's pretty nice project , it's resume material. think afraid of. however, want give proper credit collaborators.
  • i know whole point of open-source: collaboration, don't want idiot , no these people want help.
  • lately haven't had time code on project, use help.

also, i'm bit reluctant let work on project. if they're, pardon expression, noobs? suppose can rollback they're changes , tell them to, pardon expression, gtfo, wouldn't particularly nice.

how usually done?

have different levels of contribution.

start taking patches everyone. don't have accept them - if rejecting patch, explain why rejected , can done improve it.

for accepted patches, clean them (and document cleanups in coding style guide).

the people providing , best patches access repository directly , start accepting patches themselves.

at point, accept fact project no longer yours, though may want continue , lead it.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -