# Thoughts on a Development-specific engagement

**URL:** <https://community.anytype.io/t/thoughts-on-a-development-specific-engagement/25406>\
**Category:** Talk\
**Tags:** Community\
**Created:** [November 20, 2024, 3:52am UTC](https://community.anytype.io/t/thoughts-on-a-development-specific-engagement/25406 "2024-11-20T03:52:29Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![Shampra](https://community.anytype.io/user_avatar/community.anytype.io/shampra/32/8056_2.png) [@Shampra](https://community.anytype.io/u/Shampra)\
**Post date:** [November 22, 2024, 10:08pm UTC](https://community.anytype.io/t/thoughts-on-a-development-specific-engagement/25406/21 "2024-11-22T22:08:26Z")

</div>

For the context, I wanted to participate on the Anytpe-ts part…

- a few small pull requests accepted
- other PRs refused because middleware was the preferred solution or because it was a design issue.

I’d started other work (in particular, to have [displayable relations on previews](https://community.anytype.io/t/add-featured-relations-option-to-object-preview-menu/8441/2), which I thought was cool) but I preferred to stop.

Some ideas if the team wants to encourage developers to help:

- **Better communication**  
– Have a way of discussing development proposals with the team, before and during progress. Technical discussion: in my opinion, the forum is not suitable.  
The objective is to have support if we have technical questions or to validate our ideas. No reaction, no answers, discourages participation!  
– And when you submit a PR, avoid refusals without a discussion to explain why. You have your reasons, but after hours of work for us, getting a “no, that’s design” stings.  
– And since that’s a setback for both you and us: make sure you indicate somewhere what you accept and what you don’t!  
Don’t do anything involving deisgn, UX, UI? Okay, but you have to make it known too.

- I think this is still a work in progress: **better integration between the different tools** would be nice. We don’t have access to your Linear, so it’s impossible to know if this or that is already in progress. And sometimes Github and the forum overlap.

- An **ever better documented code**  
As for the code, it’s more or less commented on depending on the part. It’s always a pity, but in an open-source project, it seems to me essential to document functions, comment on the whys and wherefores of certain parts, etc. When it’s well done, it’s not a problem.  
When it’s well done, there’s really no need for further documentation.

Please also note that in “ **Help wanted** ”, there is no link for the development part. If you want one, you’ll have to show it a bit more ;-).

**So the main thing is to communicate and define a clear, documented process.**  
I see something I’d like to work on on the forum or Github → I open a participation request (specifying what I’m proposing - technical or design) → I’m given the Go or I’m told what’s going to get in the way → Exchange along the development path if necessary → All good!

This may require some time dedicated to this follow-up, especially if it develops… but it will also be development gained!

PS : and nothing to say about licence, it’s open-source according to the accepted definition (generally…). As I don’t intend to resell Anytype in my neck of the woods, I have nothing to say against the current version.

---

_[View the full topic](https://community.anytype.io/t/thoughts-on-a-development-specific-engagement/25406)._