@evan Oh noooo
I'm going to have one of those weeks.
Bonjour à tous,
Vous seriez gentil de « Booster/favoriser/liker » ce message, car je fais une démonstration du Fedivers à mon ami Romain.
Salutations spéciale à mon ami @cb_sourire.
@emoji__polls AERIAL TRAMWAY
@stepheneb @fathermcgruder @knud @sundogplanets Possibly relevant…?
@evan @stefan
@evan IMO, this is basically the world as it is. However it leads to a problem I experience all the time: I am stuck doing maintenance scut work and making sure everything is done correctly, and no time to work on the cool features that I started the entire project go work on. Once you display competence at that level, it will fill all your time.
So, given this, I'm going to say 25-50%. Core contributors work on core features and provide stability and performance, and casual contributors work on features, plugins, or extensions. Leveraging that big community is a good goal, but expertise matters, too.
I think both types of contributors provide different value to a project. Core contributors provide long-term vision, stability, and a holistic perspective on architecture. Casual contributors are usually more directly representative of user needs, can provide fresh perspective and out-of-the-box thinking, and can concentrate on low-priority problems.
@wendinoakland @fathermcgruder @knud @sundogplanets
You can add a Note that is associated with a user.
I would love it if Block was something I could initiate while viewing a post and optionally the “adding a Note ui” appeared with the post link already copied into the content.
Doing some research has amended that a bit. In particular, Bird et. al. 's "Don't Touch My Code" shows that there is a strong ownership effect on code quality. That is, developers with longtime relationships to a codebase can reduce defect rates.