Quick-doc on Jitsi video-conferencing in Fedora? #331

Closed
opened 2021-01-26 09:58:46 +00:00 by lcts · 8 comments
Contributor

I've wrote a guide over on ask.fp.o on how to set up a Jitsi server on Fedora.
Would it make sense to turn that into a quick-doc?

It might not be 'official' enough for the quick-doc pages, though, given that it relies heavily on my Copr packages, though I would probably include a section of how to do the same using upstream's container images.

I've wrote a guide over on ask.fp.o on how to [set up a Jitsi server on Fedora](https://ask.fedoraproject.org/t/howto-jitsi-videoconference-server-on-fedora/10800). Would it make sense to turn that into a quick-doc? It might not be 'official' enough for the quick-doc pages, though, given that it relies heavily on my Copr packages, though I would probably include a section of how to do the same using upstream's container images.

Sorry for the "late" response. We are in the process to revive the docs team.

That said, and just in case we can ignore the 2 years gap, an installation guide about jitsi would be great. Either as Quick Doc or as a Server Example Use Case (https://docs.fedoraproject.org/en-US/fedora-server/)

Sorry for the "late" response. We are in the process to revive the docs team. That said, and just in case we can ignore the 2 years gap, an installation guide about jitsi would be great. Either as Quick Doc or as a Server Example Use Case (https://docs.fedoraproject.org/en-US/fedora-server/)
Contributor

Issue tagged with: good first issue

Issue tagged with: good first issue
Contributor

Metadata Update from @quiet:

  • Issue assigned to quiet
**Metadata Update from @quiet**: - Issue assigned to quiet
Contributor

Hello @lcts,
I started documenting your proposal in the Quick Docs. Would you agree to review my work, once I have some draft?

Thanks,

Hello @lcts, I started documenting your proposal in the Quick Docs. Would you agree to review my work, once I have some draft? Thanks,

@quiet & @lcts : Well, I processed the pull request and the article is online now.

The PR apparently contains duplicates. Is this intended?

The COPR link refers to a package that is more than a year old and, as far as I know, is not the current version. Is there an update planned?

@quiet & @lcts : Well, I processed the pull request and the article is [online](https://docs.fedoraproject.org/en-US/quick-docs/getting_started_with_jitsi/) now. The PR apparently contains duplicates. Is this intended? The COPR link refers to a package that is more than a year old and, as far as I know, is not the current version. Is there an update planned?
Contributor

@quiet & @lcts : Well, I processed the pull request and the article is online now.

The PR apparently contains duplicates. Is this intended?

The COPR link refers to a package that is more than a year old and, as far as I know, is not the current version. Is there an update planned?

@pboy in this case that's why I prefer using jitsi under docker, please see my comment:

https://discussion.fedoraproject.org/t/howto-jitsi-videoconference-server-on-fedora/78672/2

Regards.,

> @quiet & @lcts : Well, I processed the pull request and the article is [online](https://docs.fedoraproject.org/en-US/quick-docs/getting_started_with_jitsi/) now. > > The PR apparently contains duplicates. Is this intended? > > The COPR link refers to a package that is more than a year old and, as far as I know, is not the current version. Is there an update planned? @pboy in this case that's why I prefer using jitsi under docker, please see my comment: https://discussion.fedoraproject.org/t/howto-jitsi-videoconference-server-on-fedora/78672/2 Regards.,

OK, I added a warning, but leave it online for the time being.

OK, I added a warning, but leave it online for the time being.

Metadata Update from @pboy:

  • Issue close_status updated to: stale
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @pboy**: - Issue close_status updated to: stale - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Docs/quick-docs#331
No description provided.