#fedora-flock-picasso: Pagure: Past, Present, and Future - Speaker: Pierre-Yves Chibon (pingou)
Meeting started by jflory7 at 13:33:36 UTC
(full logs).
Meeting summary
- Introduction (jflory7, 13:33:43)
- Talking about Pagure, open source git
forge (jflory7,
13:33:54)
- Background (jflory7, 13:34:00)
- Fork, pull request, three repositories per
project (sources, pull requests, tickets) (jflory7,
13:34:21)
- New UI, new architecture, and lots of new
features with recent growths (jflory7,
13:35:06)
- Architecture (jflory7, 13:36:21)
- Diagram on-screen of how all of Pagure
architecture fits together (see slides / video feed later)
(jflory7,
13:36:53)
- EventSource server: If two people working on
ticket / PR, one is making comment, new comment magically appears on
other user's page (jflory7,
13:38:20)
- Gitolite has always been a part of the project
for managing user git repos and projects (jflory7,
13:39:56)
- Features (jflory7, 13:39:59)
- Doc hosting / repos (jflory7,
13:40:03)
- To generate docs, you push source to the docs
repo, view page, and updates quickly and instantly (jflory7,
13:41:59)
- https://docs.pagure.org/pagure/
(jflory7,
13:42:16)
- === Watch project (Gaurav Kumar) ===
(jflory7,
13:42:55)
- Watch a project, get notifications as if you
had commit rights (except on priv. tickets) (jflory7,
13:43:22)
- === Roadmap === (jflory7,
13:43:55)
- Migrating Trac features to Pagure was a major
focus, like roadmaps (jflory7,
13:44:31)
- === Customized PR page === (jflory7,
13:45:57)
- You can customize the information displayed in
pull requests (jflory7,
13:46:49)
- Includes what branch and repo pull requests go
into, add a note about contributing (e.g. "how to test your changes
before submitting") (jflory7,
13:47:22)
- === Issue templates === (jflory7,
13:48:10)
- Different issue templates for different ticket
types (jflory7,
13:49:24)
- === Diff between x commits (Oliver Guitierrez)
=== (jflory7,
13:49:39)
- https://pagure.io/pagure/c/5803a79..3c85bbc
(jflory7,
13:50:08)
- Q: "Can we compare against dates? e.g. Jan 1
and Mar 30?" (jflory7,
13:50:36)
- A: Currently not, only two commits. Technically
possible, no reason why not. Merge commits could affect whether this
is accurate or not as well, e.g. if changes were made before date,
but were merged in during that timeframe (jflory7,
13:52:07)
- === Take issue (Ryan Lerch) === (jflory7,
13:52:43)
- Before, if you wanted to take an issue, you
needed to edit metadata, find your username, save metadata
(jflory7,
13:53:11)
- Now, you click the button in the issue and you
will auto-assign it to yourself. No refresh necessary (jflory7,
13:53:28)
- Q: "Right now, if you have page open for a long
time, will it work?" (jflory7,
13:53:47)
- A: Will work because connection never closes.
Problem is that some endpoints is over cross-site scripting, other
concerns as well were considered too. (jflory7,
13:54:50)
- === Live completion (Eric Barbour) ===
(jflory7,
13:55:01)
- Auto-completion for tagging username or IDs for
tickets / PRs, e.g. @jflory7 or #17 (jflory7,
13:55:27)
- === README file at creation (Ryan Lerch)
=== (jflory7,
13:56:08)
- Most people used to git, not a problem, but
more in mind for new users (jflory7,
13:56:18)
- === Fake namespace === (jflory7,
13:57:00)
- Want to have Pagure as front-end for
dist-git (jflory7,
13:57:19)
- Run x instances of Pagure for x instances of
pkgdb, not effective solution when you can just run one. Won't be
able to search between Pagures. (jflory7,
13:58:16)
- Adding namespacing would break all previous
projects and change all URLs for all projects (jflory7,
13:58:43)
- Solution? Adding one slash to the end of a
project configuration (jflory7,
13:59:48)
- === New hooks === (jflory7,
14:02:54)
- ReadTheDoc hook: Push to PAgure, update
ReadTheDocs (jflory7,
14:03:14)
- Block un-signed commits: Blocks PRs from being
merged if they are unsigned with GPG (jflory7,
14:03:37)
- Block non-fastforward commits: If you want to
keep the log clean, keeps merge commits out and only relevant
commits (can also specify which branch to have this apply to, e.g.
`master`) (jflory7,
14:04:26)
- === Better Pagure hook === (jflory7,
14:04:32)
- Close ticket / PR via commit message (e.g. `git
commit -s "close issue #10 close pull request #6"`) (jflory7,
14:05:11)
- Future (jflory7, 14:05:42)
- === Private repository (Farhaan) ===
(jflory7,
14:05:55)
- === CI integration (Farhaan) === (jflory7,
14:07:11)
- Pull requests can have flags to automatically
build projects on other services, e.g. Jenkins (jflory7,
14:07:28)
- Aimed for next release (jflory7,
14:07:32)
- === Front-end for pkgs.fp.o (Vivek Anand)
=== (jflory7,
14:08:04)
- http://pkgs.stg.fedoraproject.org/pagure/
(jflory7,
14:10:19)
- Work in progress, but implementation is public,
in staging (jflory7,
14:10:22)
- Q: "Can I do stuff with this or will it break
things?" (jflory7,
14:10:24)
- A: Shouldn't break anything, but if it does, we
need to look into it! (jflory7,
14:10:26)
- === Mirror sources === (jflory7,
14:11:41)
- Designed to be made so you can move things from
Pagure instance to Pagure instance (jflory7,
14:11:52)
- Maybe you have a private Pagure instance and
want everyone to be on there, should be able to port all packages
over to the other instance (jflory7,
14:12:26)
- When you push to Pagure, it will do a git push
to another git server (jflory7,
14:12:43)
- Community (jflory7, 14:13:09)
- 56 contributors, 33 contributors at 1.0, 2 GSoC
students this year (Vivek Anand & Farhaan Bukhsh), 2 Red Hat
interns (Eric Barbour and Simon) (jflory7,
14:13:51)
- Top 10 contributors: pingou, ryanlerch,
farhaanbukhsh, Johan, Clement, Vivek, Farhaan, Sayan, LubomÃr,
puiterwijk (jflory7,
14:14:50)
- Being packaged in Debian (jflory7,
14:16:34)
- Used outside our community (jflory7,
14:16:37)
- https://git.48.io (jflory7,
14:16:41)
- https://git.pignus.computer
(jflory7,
14:16:44)
- Evaluated by two start-ups (and a team at
RackSpace!) (jflory7,
14:16:53)
- Questions (jflory7, 14:17:36)
- Q: "When is dist-git for Fedora going to be in
prod?" - mattdm (jflory7,
14:17:57)
- A: As soon as we support it! It just reached
staging, not entirely deployed (jflory7,
14:19:23)
- Q: "Is it designed in a way to work around
problem by packaging dist-git into pagure.io?" - mhroncok
(jflory7,
14:21:58)
- A: Leverage pagure.io for pkg apps and
relationship between fork and where it's coming from (jflory7,
14:22:09)
Meeting ended at 14:24:12 UTC
(full logs).
Action items
- (none)
People present (lines said)
- jflory7 (181)
- zodbot (19)
- jibecfed (1)
Generated by MeetBot 0.1.4.