github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Local polls in Issues #3913

New Issue
Open
opened 2025-11-02 05:30:25 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-02 05:30:25 -06:00
Owner
Copy Link

Originally created by @Scharunge on GitHub (Sep 6, 2019).

  • Gitea version (or commit ref):
  • Git version: 1.9.2
  • Operating system: Windows
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

Description

Feature Request

There is a posibility to create polls via https://app.gh-polls.com/ which is a great thing. Apparently I can't use this soulution due to company policy. Its not allowed to store information of any kind on external resources.

It would be nice if I could create a poll directly in a gitea issue.

Originally created by @Scharunge on GitHub (Sep 6, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: 1.9.2 - Operating system: Windows - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite ## Description ### Feature Request There is a posibility to create polls via https://app.gh-polls.com/ which is a great thing. Apparently I can't use this soulution due to company policy. Its not allowed to store information of any kind on external resources. It would be nice if I could create a poll directly in a gitea issue.
GiteaMirror added the type/proposal label 2025-11-02 05:30:25 -06:00
GiteaMirror commented 2025-11-02 05:30:26 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (May 3, 2020):

It would be nice if I could create a poll directly in a gitea issue.

We're experimenting (day 1) with Go and Gitea and trying to rank issues (quality?, urgency, importance) using Majority judgment (MJ). It would be nice to cover the case of "inline", markdown-created polls too. How do you envision setting it up in markdown? goldmark looks quite extensible.

Since we're absolute beginners both in Go and Gitea, enlightened supervision and guidance would not go amiss.

So far we see the following new models:

  • Poll
  • Vote (Judgment)
@domi41 commented on GitHub (May 3, 2020): > It would be nice if I could create a poll directly in a gitea issue. We're experimenting (day 1) with Go and Gitea and trying to rank issues (quality?, urgency, importance) using [Majority judgment (MJ)](https://en.wikipedia.org/wiki/Majority_judgment). It would be nice to cover the case of "inline", markdown-created polls too. How do you envision setting it up in markdown? `goldmark` looks quite extensible. Since we're absolute beginners both in Go and Gitea, enlightened supervision and guidance would not go amiss. So far we see the following new models: - _Poll_ - _Vote_ (_Judgment_)
GiteaMirror commented 2025-11-02 05:30:26 -06:00
Author
Owner
Copy Link

@shubham8agar commented on GitHub (Nov 30, 2022):

This will be great to add such feature/enhancement in issues. This will help collaborators to make judgement over a issue which require opinions from multiple people.

@shubham8agar commented on GitHub (Nov 30, 2022): This will be great to add such feature/enhancement in issues. This will help collaborators to make judgement over a issue which require opinions from multiple people.
GiteaMirror commented 2025-11-02 05:30:26 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Dec 22, 2022):

Our PoC works and integrates quite nicely with Gitea. Example:

image

I've had to pause dev, though, because I needed to pay rent and I could not find funding for this. Would love to keep at it, especially with the liquid (delegative) features, since we have some (theoretical) algorithms that look quite nice.

@domi41 commented on GitHub (Dec 22, 2022): Our PoC works and integrates quite nicely with Gitea. Example: ![image](https://user-images.githubusercontent.com/24573513/209070127-c24bb5b0-b98e-4a79-b97d-b85ff3e5fa48.png) I've had to pause dev, though, because I needed to pay rent and I could not find funding for this. Would love to keep at it, especially with the liquid (delegative) features, since we have some (theoretical) algorithms that look quite nice.
GiteaMirror commented 2025-11-02 05:30:26 -06:00
Author
Owner
Copy Link

@shubham8agar commented on GitHub (Dec 22, 2022):

Our PoC works and integrates quite nicely with Gite

Is this opensource ? Can u share link ?

@shubham8agar commented on GitHub (Dec 22, 2022): > Our PoC works and integrates quite nicely with Gite Is this opensource ? Can u share link ?
GiteaMirror commented 2025-11-02 05:30:26 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Feb 16, 2023):

Is this opensource ? Can u share link ?

Technically, yes.
It's on a Gitea instance that has been overrun by bots, although we closed registration after the first few bots ; no idea how they did it.

Thankfully, I had forked on Github as well here : https://github.com/domi41/gitea/tree/mj-v1.14.3 and https://github.com/domi41/gitea/tree/mj-v1.18.3 (latest)

State of things

  • Needs integration as a plugin, but at the time it was not possible I believe, as I had to add new routes and models, and hook templates in some odd places.

  • Needs update to the latest Gitea version. (it always does)

  • The MJ (Majority Judgment) algorithm is quite efficient and should scale very well.

  • But since then it has been refactored in a standalone Golang Majority Judgment library, to be used by another software piece, the Golang CLI tool to solve MJ.

@domi41 commented on GitHub (Feb 16, 2023): > Is this opensource ? Can u share link ? Technically, yes. It's on a Gitea instance that has been [overrun by bots](https://git.mieuxvoter.fr), ~~although we closed registration after the first few bots ; no idea _how_ they did it.~~ Thankfully, I had forked on Github as well here : https://github.com/domi41/gitea/tree/mj-v1.14.3 and https://github.com/domi41/gitea/tree/mj-v1.18.3 (latest) ## State of things - Needs integration as a plugin, but at the time it was not possible I believe, as I had to add new routes and models, and hook templates in some odd places. - Needs update to the latest Gitea version. (it always does) - The MJ (Majority Judgment) algorithm is quite efficient and should scale very well. - But since then it has been refactored in a [standalone Golang Majority Judgment library](https://github.com/MieuxVoter/majority-judgment-library-go), to be used by another software piece, the [Golang CLI tool to solve MJ](https://github.com/MieuxVoter/majority-judgment-cli).
GiteaMirror commented 2025-11-02 05:30:27 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Feb 20, 2023):

@shubham8agar I rebased the thing on Gitea 1.18.3, in this branch : https://github.com/domi41/gitea/tree/mj-v1.18.3

I'm still unsure how we could write this as a plugin.
Do send me MRs if you make improvements :)

@domi41 commented on GitHub (Feb 20, 2023): @shubham8agar I rebased the thing on Gitea `1.18.3`, in this branch : https://github.com/domi41/gitea/tree/mj-v1.18.3 I'm still unsure how we could write this as a plugin. Do send me MRs if you make improvements :)
GiteaMirror commented 2025-11-02 05:30:27 -06:00
Author
Owner
Copy Link

@luwol03 commented on GitHub (Feb 20, 2023):

Why should this be a plugin?

@luwol03 commented on GitHub (Feb 20, 2023): Why should this be a plugin?
GiteaMirror commented 2025-11-02 05:30:27 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Feb 21, 2023):

Why should this be a plugin?

This is actually a very good question.
I can fathom a few motives :

  1. Easier installation into existing Gitea instances (no merge, only file additions)
  2. Easier maintenance during Gitea upgrade
  3. Easier maintenance of the Poll component itself

Someone asked me why I did not make a PR ; this is a simple proof of concept, and, besides requiring approval, integrating this further into Gitea would require some careful work in the various Administration panels, up to the INI configuration file to enable and configure things, and I"m not intimate enough with Gitea yet to undertake this right now.

Right now I'm trying to squash commits to make cherry-picking easier. Awkward.

So let me ask : what do you think it should be, if not a plugin ?

@domi41 commented on GitHub (Feb 21, 2023): > Why should this be a plugin? This is actually a very good question. I can fathom a few motives : 1. Easier installation into existing Gitea instances (no merge, only file additions) 2. Easier maintenance during Gitea upgrade 3. Easier maintenance of the Poll component itself Someone asked me why I did not make a PR ; this is a simple proof of concept, and, besides requiring approval, integrating this further into Gitea would require some careful work in the various Administration panels, up to the `INI` configuration file to enable and configure things, and I"m not intimate enough with Gitea yet to undertake this right now. Right now I'm trying to squash commits to make cherry-picking easier. Awkward. So let me ask : what do *you* think it should be, if not a plugin ?
GiteaMirror commented 2025-11-02 05:30:27 -06:00
Author
Owner
Copy Link

@luwol03 commented on GitHub (Feb 22, 2023):

So let me ask : what do you think it should be, if not a plugin ?

Directly integrated into gitea core? I understand that you are not so familiar with the gitea codebase. But I am curious if there is another argument against integrating it directly.

@luwol03 commented on GitHub (Feb 22, 2023): > So let me ask : what do you think it should be, if not a plugin ? Directly integrated into gitea core? I understand that you are not so familiar with the gitea codebase. But I am curious if there is another argument against integrating it directly.
GiteaMirror commented 2025-11-02 05:30:27 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Feb 23, 2023):

I am curious if there is another argument against integrating it directly

If there is, it won't come from me. :)
I desperately want a solid polling system.

Perhaps we should aim to consort on specs before undertaking the endeavor of deep Gitea integration ?

So far we have:

  • Feature F01: Create a Poll in a Repository with Issues (& MRs) as Candidates
  • Rule R01: Creating a Poll (F01) requires Repository Ownership
  • Feature F02: Vote on / Judge an Issue in an open Poll
  • Rule R02: Voting (F02) requires write access to the Issues

I want :

  • Rule R03: Creating a Poll (F1) requires a specific Permission
  • Feature F01-01: Configure the Grading set of a Poll (F01)
  • Feature F01-02: Target specific Issues & MRs for a Poll (F01) (done in mj-develop)
  • Feature F01-03: Set a lifetime to a Poll (F01)
  • Feature F03: Enable/Disable Polls for all Repositories (done in mj-develop)
  • Rule R04: Enabling Polls for all Repositories requires being Admin (done in mj-develop)
  • Feature F04: Enable/Disable Polls for a Repository (done in mj-develop)
  • Rule R05: Enabling Polls for a Repository requires being Owner (done in mj-develop)
  • …

The rationale behind starting with Issues as Candidates

  • Easier initial integration (at least to me)
  • We get comments, tags, all the collective discourse goodies on each Candidate
  • It's nice to rank issues by Enthousiasm or (Expected) Difficulty, Urgency, etc.
  • We can still make any poll we want, albeit it's a little tedious to add issues for each candidate, but that can be helped.

The problems I face

Inline polls that anyone can start in a comment would be amazing.

With all the strict typing going on, I'm not sure how to write things so they'll work for both kinds of candidates (Issues, and Inline). If you understand what I mean and know what I should read/know to solve this, please bring your lights 🌟 .

@domi41 commented on GitHub (Feb 23, 2023): > I am curious if there is another argument against integrating it directly If there is, it won't come from me. :) I desperately want a solid polling system. Perhaps we should aim to consort on specs before undertaking the endeavor of deep Gitea integration ? So far we have: - Feature _F01_: Create a Poll in a Repository with Issues (& MRs) as Candidates - Rule _R01_: Creating a Poll (F01) requires Repository Ownership - Feature _F02_: Vote on / Judge an Issue in an open Poll - Rule _R02_: Voting (F02) requires write access to the Issues I want : - Rule _R03_: Creating a Poll (F1) requires a specific Permission - Feature _F01-01_: Configure the Grading set of a Poll (F01) - Feature _F01-02_: Target specific Issues & MRs for a Poll (F01) _(done in [mj-develop](https://github.com/domi41/gitea/tree/mj-develop))_ - Feature _F01-03_: Set a lifetime to a Poll (F01) - Feature _F03_: Enable/Disable Polls for all Repositories _(done in [mj-develop](https://github.com/domi41/gitea/tree/mj-develop))_ - Rule _R04_: Enabling Polls for all Repositories requires being Admin _(done in [mj-develop](https://github.com/domi41/gitea/tree/mj-develop))_ - Feature _F04_: Enable/Disable Polls for a Repository _(done in [mj-develop](https://github.com/domi41/gitea/tree/mj-develop))_ - Rule _R05_: Enabling Polls for a Repository requires being Owner _(done in [mj-develop](https://github.com/domi41/gitea/tree/mj-develop))_ - … ## The rationale behind starting with Issues as Candidates - Easier initial integration (at least to me) - We get comments, tags, all the collective discourse goodies on each Candidate - It's nice to rank issues by _Enthousiasm_ or (Expected) _Difficulty_, _Urgency_, etc. - We can still make any poll we want, albeit it's a little tedious to add issues for each candidate, but that can be helped. ## The problems I face Inline polls that anyone can start in a comment would be amazing. With all the strict typing going on, I'm not sure how to write things so they'll work for both kinds of candidates (Issues, and Inline). If you understand what I mean and know what I should read/know to solve this, please bring your lights :star2: .
GiteaMirror commented 2025-11-02 05:30:28 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Feb 23, 2023):

image

A little teaser… :) I really like how wonderfully things click into place with the units. Gitea is really nice.

To proceed further:

  • figure out the duality of Candidates (Issues or Inline)
  • refactor to use the external judgment module
  • …which will enable gradation and color poll settings
  • allow targeting a subset of Issues
@domi41 commented on GitHub (Feb 23, 2023): ![image](https://user-images.githubusercontent.com/24573513/220843125-1a3d2dab-840f-4c6d-8905-3d1a2238e1d0.png) A little teaser… :) I really like how wonderfully things click into place with the `units`. Gitea is really nice. To proceed further: - figure out the duality of Candidates (Issues or Inline) - refactor to use the external `judgment` module - …which will enable gradation and color poll settings - allow targeting a subset of Issues
GiteaMirror commented 2025-11-02 05:30:28 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Nov 18, 2023):

I updated the Polls fork to Gitea 1.20.5, and improved the general friendliness of the Badge Polls.

A few tweaks aside, my general next step is to work on the Inline Polls that are the actual ask of this Issue. If you have features, specs, must-haves, and so forth, now is the time to make them known.

Note: at the time of this post, mj-develop is outdated. I will resume working on it eventually, as it is based on main.

@domi41 commented on GitHub (Nov 18, 2023): I [updated the Polls fork to Gitea `1.20.5`](https://github.com/domi41/gitea/tree/mj-v1.20.5), and improved the general friendliness of the _Badge Polls_. --- A few tweaks aside, my general next step is to work on the _Inline Polls_ that are the actual ask of this Issue. If you have features, specs, must-haves, and so forth, now is the time to make them known. --- Note: at the time of this post, `mj-develop` is outdated. I will resume working on it eventually, as it is based on `main`.
GiteaMirror commented 2025-11-02 05:30:28 -06:00
Author
Owner
Copy Link

@domi41 commented on GitHub (Dec 4, 2023):

image

I've updated mj-develop with some changes, polishing the badge poll feature a little bit, while experimenting refactoring for inline polls.

We can now choose amongst multiple available gradings (formerly gradations), as you can see in the screenshot above, using animals instead of emotes.

@domi41 commented on GitHub (Dec 4, 2023): ![image](https://github.com/go-gitea/gitea/assets/24573513/cadec652-c740-4da6-99fc-26e5b9f049c2) I've updated [mj-develop](https://github.com/domi41/gitea/tree/mj-develop) with some changes, polishing the _badge poll_ feature a little bit, while experimenting refactoring for _inline polls_. We can now choose amongst multiple available _gradings_ (formerly _gradations_), as you can see in the screenshot above, using animals instead of emotes.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3913
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?