Maybe it's time to open up this repo?

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
devops, infrastructure

Research direction

Start with the repository visibility request in issue #19 and the mentioned config.json for an HTTPS site. Clarify whether the intended outcome is opening the repository, adding HTTPS setup configuration, or both; the issue is done only when that scope and the required repository changes are agreed.

Written by the indexing model from the issue text.

Description

I still have more work I want to do here, but it's small stuff. Like for example, I want to put up a config.json specifically for an HTTPS site. Or perhaps this is something someone else could do.

I'd like to send links to questions in this repo to people who aren't members. That would be my main reason for wanting to open it up. To take out the friction of having someone authorized to read this.

The reason, lack of stability, is not so much an issue now.

Dominant language
HTML
Stars
11
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/feedlandInstall

All issues in scripting/feedlandInstall

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.