sipb / badges Goto Github PK

No fancy digital graphics can be easily made without the pen

May purchase a new one soon

Pen lost in walounge, den of foxgirls, or moose watcher's room eom.

• decide database schema
• decide how badges assets are stored and served (image and desc.)

Make html templates for a landing page, badge page, and user page.

add a project description to readme file, describing the objective of project plus some other good info

• design front-end mock (front page, badges, users)
• design front page html template
• design badges page html template
• design users page html template

There have been a lot of talks lately about replacing the term master in git because of it's historical relation to slavery. Recently, GitHub changed it's default branch name for new repositories to main. Git also allows users to set their own default name for main branch. I think we should support this move since the process is easy enough. I already created a copy of master called main. All we have to do now is to change the default setting in GitHub and delete master branch. I haven't done these last two things because I want to hear from the other team members first.

If we have a go, I'll take care of changing the name change. The only thing you have to do, and you only have to do this if you are working on a local clone of master branch, is execute the following.

# Switch to the "master" branch:
$ git checkout master

# Rename it to "main":
$ git branch -m master main

# Get the latest commits (and branches!) from the remote:
$ git fetch

# Remove the existing tracking connection with "origin/master":
$ git branch --unset-upstream

# Create a new tracking connection with the new "origin/main" branch:
$ git branch -u origin/main

httpS://github.com

as title suggets

Script to generate full badge from
badge ID, user ID, template, & img

This is for separation of images (which are static assets) and code. When cloning the repo to work on code, we generally don't want to download images. Images are usually served by a different server anyway.

The problem

The way we are pushing code to the sipbbadges locker allows erroneous code to be pushed to the locker. We also have no way of knowing what version of the code exist in the locker. We also have no way of putting more than one repository inside web_scripts. In general, the way we are doing development is not good.

The solution

Change the project structure to adopt Django best practices. We should not put the whole web_scripts folder into one git repo. Multiple repos should be able to exist in the folder. For redirect purposes, we just edit .htaccess to let Apache server know where to redirect.

fair & transparent process to get badges

who can award badges? (members/keyholders/badges comm)
witnesses required?
can't give to self?
automatic vs manual badges