Development Process

Hi there!

For lack of time, I’m hardly using Discord, so I am posting here. I had this in
the line before the migration mishaps. So please, do not read this post as an
indirect response to that event.

I appreciate this experiment you are doing! Mostly because it has quite some
originality in its ideas and from most what I see you have an honest desire to
make an actual contribution. I think pride is possibly also involved, but that
shall be deserved, if it doesn’t harm the overall outcome.

I’ve read that a new site is in development, but still, I’d like to have some
feed-back on my thoughts.

I wonder: Is pickle-finance intended to become like an enterprise, with
community involvement (code contributers are limited to a core team), or a project
that is owned and developed by the community (virtually anyone can contribute,
given that changes are approved by a core team)?

This is meant as an honest question, that I do not see answered anywhere. I
think both are fine, but they surely influence my excitement.

I would like the new site to have a FAQ to answer these kind of questions.
Also there could be a list of guides (to not say rules), of how to behave. For
one, the “Your proposals don’t matter” post was a very good one to list there!

What I’m not too happy about are the hidden development cycles. It would take
some of my uneasiness to deposits funds or hold $pickles if I could follow
development more closely. Be it for the website or the repository used for
developing the contracts (as apposed to just the “compiled” contracts).

I assume the development is hidden in this way to gain a surprise momentum
and/or to maintain an advantage over competitors while developing new ideas? Or
to not loose face in case of mistakes? I guess there’s no harm to keep them
hidden, for now!

… Eventually I would like to see, that

  1. community can contribute to site development
  2. community can investigate the quality of the general development cycles, to
    build trust (The commit messages in the repositories look like you are using
    the github web interface? To guard your anonymity while using tor or something?)
  3. community can contribute to contract development by making PRs or doing PR-reviews
  4. there is a step-by-step process involved for deploying new contracts/code.
    Not trying to take the fun out of it, just the minimal stuff, so it is always
    clear what is happening next. (i.e. changes are made by a PR. They need
    approval. After merge they can be deployed on a testnet. Something like that)

Additionally, I am motivated to try my hand on some UI to visualize the
mechanics of the contracts. Listing transactions at first, but hopefully having
some kind of flow diagram displaying what is happening under the hood. I’d
rather know in advance if something like that is already being worked on. That
would be a waste of resources.

Cheers!

1 Like

Hi @sworb!

I wonder: Is pickle-finance intended to become like an enterprise, with
community involvement (code contributers are limited to a core team), or a project
that is owned and developed by the community (virtually anyone can contribute,
given that changes are approved by a core team)?

The goal is to slowly evolve into a project that is owned and developed by the community. Right now it might not seem like so as we don’t have a good on-boarding/management/list-of-things-we-would-like yet. Do you think a basic kanban style github project board is sufficient? If not, do you have any other ideas?

What I’m not too happy about are the hidden development cycles. It would take
some of my uneasiness to deposits funds or hold $pickles if I could follow
development more closely. Be it for the website or the repository used for
developing the contracts (as apposed to just the “compiled” contracts).

Good point, I’ve made the contracts repository public

There is no “hidden” development cycles. The repositories are mainly private to prevent us from accidentally doxing ourselves.

Eventually I would like to see, that
1. community can contribute to site development
2. community can investigate the quality of the general development cycles, to
build trust (The commit messages in the repositories look like you are using
the github web interface? To guard your anonymity while using tor or something?)
3. community can contribute to contract development by making PRs or doing PR-reviews
4. there is a step-by-step process involved for deploying new contracts/code.
Not trying to take the fun out of it, just the minimal stuff, so it is always
clear what is happening next. (i.e. changes are made by a PR. They need
approval. After merge they can be deployed on a testnet. Something like that)

1, 2, 3: Definitely
4. Noted, I’ll get some Ops setup

3 Likes

Hi @0xpenguin!

Thanks for taking the time to reply. Much appreciated.

I think a basic kanban style github project will suffice indeed.

I understand that this is a concern, if you want to stay anonymous, which again, is also understandable. I myself have to many trails on the internet, that I stopped bothering much. Wish I had taken more care.

That is looking good, thanks! :slight_smile:

PS: Don’t expect any major contributions from me anytime soon, as my solidity knowledge is basically nil. I still enjoy reading them codes, though.

1 Like