CursiveHello,
@CursiveHello@bitbang.social avatar

What should I know before open-sourcing my program?

My goal is to improve it by letting people submit changes, and making it easier for me to ask for help. I would still make the final call on decisions.

(Blog posts welcome! Boost if you care. The program is @songpocket)

Crell,
@Crell@phpc.social avatar

@CursiveHello @songpocket Have a CoC. Enforce it from day 0. If someone objects to you having a CoC, they're being helpful as self-identifying as someone who will be a problem so you should ban them in advance.

Crell,
@Crell@phpc.social avatar

@CursiveHello @songpocket If you actually want people to use it, treat it like a product, not a tool: Consider the experience of installing and using it the first time. How do they get from zero to "hey, cool!" in as little time as possible?

Crell,
@Crell@phpc.social avatar

@CursiveHello @songpocket The second worst thing that can happen is that no one uses it.

The actual worst thing that can happen is a whole lot of people use it, and start demanding support.

regis,
@regis@phpc.social avatar

@CursiveHello @songpocket - provide a nice readme so people know how to use it, install it, or contribute

  • don't forget to add a licence, whatever that is
  • indicate whether you plan to maintain it for a long time or not
  • do not merge something you are not comfortable with, since you will be the one who will have to maintain forever
  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • DreamBathrooms
  • magazineikmin
  • ethstaker
  • InstantRegret
  • tacticalgear
  • rosin
  • love
  • Youngstown
  • slotface
  • ngwrru68w68
  • kavyap
  • cubers
  • thenastyranch
  • mdbf
  • provamag3
  • modclub
  • GTA5RPClips
  • normalnudes
  • khanakhh
  • everett
  • cisconetworking
  • osvaldo12
  • anitta
  • Leos
  • Durango
  • tester
  • megavids
  • JUstTest
  • All magazines