Repository name poll! Yayer!!
Poll

What URL for the best forum software ever? (Pending independent reviews.)

github.com/Wedge/
5 (55.6%)
github.com/wedge/
3 (33.3%)
I'm Nao, I don't want to influence votes, or whatever.
1 (11.1%)
Total Members Voted: 9

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Repository name poll! Yayer!!
« Reply #15, on January 16th, 2014, 06:12 PM »
Actually I remembered that since only I have push rights to that account, no one is likely to have already added it as a remote... ;)

I'll keep watching the poll until I've committed all my bug fixes and am ready to push.
Tomorrow should be good.
I caught a cold this morning so it made things slower...

kimikelku

  • Posts: 61
Re: Repository name poll! Yayer!!
« Reply #16, on January 16th, 2014, 07:04 PM »
I have voted wedge/wedge too, but will it cause a problem too for the language repo?

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Repository name poll! Yayer!!
« Reply #17, on January 16th, 2014, 08:04 PM »
Well, not really, unless you have it as a local remote, in which case you'll just need to update it. (git remote remove and git remove add or something, or simply TortoiseGit > Settings > Git > Remote, change casing, save.)

(I'm leaning towards Wedge/wedge currently, but... Whatever? I won't push today anyway. Too risky with the installer problems.)

Re: Repository name poll! Yayer!!
« Reply #18, on January 18th, 2014, 03:34 PM »
JK but this comes to mind, when thinkng of all the work you've gone through and the trying times lol!

wedgie

attached: remember JK!

regards,.
Maxx

 Wedgie.jpg - 26.16 kB, 400x300, viewed 158 times.


Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Repository name poll! Yayer!!
« Reply #19, on January 18th, 2014, 03:57 PM »
Oh, you have no idea...
Just this topic: I'm learning towards NOT using the lowercase 'wedge' as account name, but the majority voted for it, and I don't like being unpleasant... :^^;:

As for the rest...

Well, the problem with going public is not that people will be exposed to my code and thus able to criticize it. Not only am I ready for that, but I'm confident that everyone skilled enough to understand what's under the hood will be thrilled by what they'll see.
However, because git allows rewriting history, but makes one's life miserable if you attempt to force push a rewritten history to a repo that's already public[1], once the source code is public, I won't be able to rewrite history, and believe me, rewriting is REALLY cool if you're looking into having a clean repo with easy and fast blames. (Blame is a VERY useful tool which lets you find a line in a specific file, and gives you a full history of that line, i.e. the dates and contents of each successive modification to that line.)

I'm also still not sure about the new folder structure. While /app and /html are acceptable folder names because they're noob-friendly and match all of my demands, I have to say that I have to look twice for the /templates folder, before I remember it's now called /html. Oddly, it didn't take long for me to assimilate that /Sources is now /app, so I just need some time. The main problem is that /core (their parent folder) is still kind mixed up with two other sibling folders starting in 'c', i.e. 'cache' and 'css'. I'm considering renaming 'cache' to 'files', and move 'css' and 'js' inside it, which would make for a cleaner folder list, at the cost of 6 more bytes per filename in the HTML source code. Perhaps if I could find another name like 'files', but a bit shorter... ('bits'??) Or maybe I just shouldn't bother. The reason why /css and /js were made into root folders in the first place was not that it made for shorter URLs (it was a reason, but not my first), it was that it made it easier for me to clear the CSS and JS caches manually. But since I added a menu command to clear all cache, there's no reason for that any longer, eh...

These are the last few hiccups I'm having. The rest, I guess I can live with.

Also, I'm not releasing anything tomorrow, because it's the 19th, and '9' in Japanese means 'pain'. I'm a bit superstitious about Japanese numbers, to each their own. I thought today was the 19th, so I was planning to postpone to tomorrow, but right now I'm torn between releasing *now*, or postponing for another two days (and thus getting laughed at.)

First-world problems™, I know...!
 1. Basically, it just forces everyone else to delete their local repo, re-download the remote repo, and not kill the one who rewrote history. Additionally, github or git never really tell the user about that rewrite. Nuff said, it's a recipe for disaster.

Re: Repository name poll! Yayer!!
« Reply #20, on January 18th, 2014, 04:14 PM »
Maybe wat too later or way wrong, I was thinking is wedge not a cms?
wedge/cms
wedge/sys

sorry but I'm way dumb with this kind of stuff! :(

regards,
Maxx

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Repository name poll! Yayer!!
« Reply #21, on January 18th, 2014, 04:24 PM »
Well, it's not about the repo name, it has to have 'wedge' in it anyway, and 'wedge/wedge-cms' or 'wedge/wedgeforum' is probably a bit much. Wedge will have to stand by itself as not needing an introduction, so no reason to add 'forum' to it.

And no, it's not too late or anything.
I'm more interested in feedback regarding my last post above, though... ;)

Re: Repository name poll! Yayer!!
« Reply #22, on January 18th, 2014, 04:32 PM »Last edited on January 18th, 2014, 05:16 PM by Maxx
Not sure if this is of any help, but when I do a theme and add an additonal directory to it, I just use like "/mx" for my files or /img for my image files... could /na work? or am I still lost?

Edit: /mx/styles.css
              responsive.css
       /mx/script.js
              responsive.js
              jQuery.js
       /mx/img/
             all my images

regards,
Maxx

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: Repository name poll! Yayer!!
« Reply #23, on January 18th, 2014, 05:18 PM »
'Open' - because the folder contains files that are open (I assume).

And if you release Monday 0030 it'll be the 20th where you are but still Sunday everywhere west.

Suki

  • Posts: 59
Re: Repository name poll! Yayer!!
« Reply #24, on January 18th, 2014, 05:31 PM »
I voted for github.com/Wedge/wedge  using Wedge to reference the actual github account and wedge for the product seems easier to handle and understand.

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Repository name poll! Yayer!!
« Reply #25, on January 18th, 2014, 05:56 PM »
@Farjo> That would imply me going to bed right after releasing it. I need to be around to fix any problems in the first few hours... (Assuming more than a couple of people are going to download it. Ah, ah.)
Anyway, I already said last week that my target date was Jan 20, and that's the day it will be out. Probably. :P
The whole 'laugh at me' thing is if I fail to release it on the 20th, not Sunday. I just thought that Sunday was the 20th.

@Suki> I thought you'd say Wedge/Wedge, given that all of your repos are ucfirst'ed... ;)
And again, the account is Wedge, but it can still be renamed to wedge. All it changes is that the few people (I think, two!) who forked the languages repo will need to update their remotes IF they ever get writing rights on it in the future (which is not very git-like.)
I guess I'm worried about nothing. It's just a symbol of my fear of releasing, as mentioned above.
Re: Repository name poll! Yayer!!
« Reply #26, on January 20th, 2014, 03:35 PM »
I've updated the poll for simplicity.
A majority of voters (13 out of 18) chose 'wedge' for the repository name (over 'Wedge' and 'forum'), so this will be its name.
The vote on the account (organization) name was more split (5 versus 8 out of these 13), though, and I'd like to give it another go before it's too late. ;)

Let's give it a few hours, then! I guess I'll settle at the last minute.

Drunken Clam

  • Drool, drool, drool....!
  • Posts: 153
Re: Repository name poll! Yayer!!
« Reply #27, on January 20th, 2014, 04:06 PM »
Although I'm a follower of the lowercase style, in this instance, github.com/Wedge/ is easier on my ageing eyes! :whistle:

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Repository name poll! Yayer!!
« Reply #28, on January 20th, 2014, 07:09 PM »
I just realized what's wrong with me...
github.com/Wedge -> looks better in small fonts, or when the github part is ommitted (e.g. the repo's page header, 'Wedge / wedge')
github.com/Wedge -> looks better in large fonts, but looks horrible in the repo's page header ('wedge / wedge').

So, the feeling I have when I see a github URL (or a bitbucket URL, but it's private) is dependent upon the current font size, AND the place where the account name is being shown, AND whether or not it has 'github.com' before it.

Must be the silliest reason ever, but... Well, whatever. Just goes to show that I'm never, never going to be 100% happy about this tiny little detail.
If a team of people can work for a year on a competitor that has a terribly sounding name[1], when they had a perfect name to begin with[2], it's probably that it doesn't matter THAT much... Eh, what can I say!
 1. Is it a tree, or an animal? Is it a Basque word, or a mix between English and Italian?
 2. 'Dialogo' sounded so nice, I could have used it for Wedge and be happy with it.

Suki

  • Posts: 59
Re: Repository name poll! Yayer!!
« Reply #29, on January 20th, 2014, 07:49 PM »
I created my repos long before knowing what I was doing so there isn't any consistency between them. I wouldn't worry that much, just avoid changing it in the future.

Since theres a tendency in github to add silly names to your projects I usually avoid reading the name and go straight for the description/readme.