Browse Source

unify project name

Davide Alberani 7 years ago
parent
commit
aad48c41af
6 changed files with 12 additions and 12 deletions
  1. 2 2
      README.md
  2. 2 2
      angular_app/index.html
  3. 1 1
      backend.py
  4. 3 3
      docs/DEVELOPMENT.md
  5. 1 1
      eventman_server.py
  6. 3 3
      utils.py

+ 2 - 2
README.md

@@ -1,9 +1,9 @@
-Event Man(ager)
+EventMan(ager)
 ===============
 
 Your friendly manager of attendees at an event.
 
-Event Man(ager) will help you handle your list of attendees at an event, managing the list of registered persons and marking persons as present.
+EventMan(ager) will help you handle your list of attendees at an event, managing the list of registered persons and marking persons as present.
 
 Main features:
 - an admin (in the future: anyone) can create and manage new events

+ 2 - 2
angular_app/index.html

@@ -1,7 +1,7 @@
 <!doctype html>
 <html ng-app="eventManApp">
     <head>
-        <title>Event Man(ager)</title>
+        <title>EventMan(ager)</title>
         <meta charset="utf-8">
         <meta http-equiv="X-UA-Compatible" content="IE=edge">
         <meta name="viewport" content="width=device-width, initial-scale=1">
@@ -111,7 +111,7 @@
 
         <nav class="navbar navbar-default navbar-fixed-bottom">
             <div class="main-footer">
-                <a href="https://github.com/raspibo/eventman/" target="_blank">Event Man(ager)</a> by RaspiBO: <a href="http://raspibo.org">wiki</a> | <a href="http://social.raspibo.org">social network</a> | <a href="http://liste.raspibo.org/wws/">mailing lists</a> | <a href="mailto:info@raspibo.org">contact</a>
+                <a href="https://github.com/raspibo/eventman/" target="_blank">EventMan(ager)</a> by RaspiBO: <a href="http://raspibo.org">wiki</a> | <a href="http://social.raspibo.org">social network</a> | <a href="http://liste.raspibo.org/wws/">mailing lists</a> | <a href="mailto:info@raspibo.org">contact</a>
             </div>
         </nav>
     </body>

+ 1 - 1
backend.py

@@ -1,4 +1,4 @@
-"""Event Man(ager) database backend
+"""EventMan(ager) database backend
 
 Classes and functions used to manage events and attendees database.
 

+ 3 - 3
docs/DEVELOPMENT.md

@@ -1,7 +1,7 @@
 Development
 ===========
 
-As of June 2016, Event Man(ager) is under heavy refactoring. For a list of main changes that will be introduced, see https://github.com/raspibo/eventman/issues
+As of June 2016, EventMan(ager) is under heavy refactoring. For a list of main changes that will be introduced, see https://github.com/raspibo/eventman/issues
 
 Every contribution, in form of code or ideas, is welcome.
 
@@ -14,7 +14,7 @@ Definitions
 - **registered person**: someone who said will attend at the event
 - **attendee**: a person who actually *show up* (is checked in) at the event
 - **ticket**: an entry in the list of persons registered at an event
-- **user**: a logged in user of th Event Man web interface (not the same as "person")
+- **user**: a logged in user of the EventMan(ager) web interface (not the same as "person")
 - **trigger**: an action that will run the execution of some scripts
 
 
@@ -82,7 +82,7 @@ Also, remember that most of the paths can take query parameters that will be use
 
 You have probably noticed that the /events/:event\_id/persons/\* and /events/:event\_id/tickets/\* paths seems to do the same thing. That's mostly true, and if we're talking about the data structure they are indeed the same (i.e.: a GET to /events/:event\_id/tickets/:ticket\_id will return the same {"person": {"name": "Mario", [...]}} structure as a call to /events/:event\_id/persons/:person\_id). The main difference is that the first works on the \_id property of the entry, the other on person\_id. Plus, the input and output are filtered in a different way, for example to prevent a registered person to autonomously set the attendee status or getting the complete list of registered persons.
 
-Beware that most probably the /persons and /events/:event\_id/persons paths will be removed from a future version of Event Man(mager) in an attempt to rationalize how we handle data.
+Beware that most probably the /persons and /events/:event\_id/persons paths will be removed from a future version of EventMan(mager) in an attempt to rationalize how we handle data.
 
 
 Permissions

+ 1 - 1
eventman_server.py

@@ -1,5 +1,5 @@
 #!/usr/bin/env python
-"""Event Man(ager)
+"""EventMan(ager)
 
 Your friendly manager of attendees at an event.
 

+ 3 - 3
utils.py

@@ -1,9 +1,9 @@
-"""Event Man(ager) utils
+"""EventMan(ager) utils
 
 Miscellaneous utilities.
 
-Copyright 2015 Davide Alberani <da@erlug.linux.it>
-               RaspiBO <info@raspibo.org>
+Copyright 2015-2016 Davide Alberani <da@erlug.linux.it>
+                    RaspiBO <info@raspibo.org>
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.