Get set up (project managers)

To begin running a community project, you need to get set up. Getting set up involves several key steps. First put your project on Tech. Then create a Tech Forum, create a Tech Wiki page, and define skills needed for your project.

Put your project on Tech

When community members go to Tech, they can browse all available projects on the Projects tab. You can't set up your project on your own though; you will need the help of an Tech administrator, such as Tim Riker.

When you contact an administrator, send him or her your project's name and the LDS Account username of the project lead. The administrator will then set up the initial project on Tech.

Once the project has been added, you can edit the project details and specify the resources you want. The following lists the various resources available to any Tech project. Many of these resources are auto-provisioned when you create a new project on Tech. (This is one benefit of running your project on Tech!)

To edit your project information:

  1. Sign in to Tech and click Projects on the top menu.
  2. Click the Management subtab, and find your project using the search filter.
  3. Click edit below your project title.
  4. Make updates as needed, and then click Save.

Here's a description of each field.

Field Description
Project Title: Community members see this title when browsing the list of projects on Tech.
Description: The description appears below the title. Keep your description brief (about one paragraph) but also enticing. If your project title isn't clear, make it clear what the project involves in the description.
Lead's username: The lead will be running the project, interacting with volunteers and establishing him or herself as the contact. You can later designate additional project leaders, but each project has just one person who is listed as the "Project Manager & Contact."
Jira Project: JIRA is a project tracking tool commonly used on software projects. You can use JIRA to track bugs, enhancements, and other items related to your project. You can use JIRA in a variety of ways not related at all to bug tracking (for example, you could use it to track writing assignments). When community members join your project, they will automatically be given access to your JIRA project.

Note: New project members are added as observers. They can't be assigned JIRA items unless you change their role.

Jira Key: The JIRA key is automatically added here; you do not need to provide one.
Jira URL: The URL for your JIRA project. Usually, the URL is a form of your project's name.
Status: You have two options: private or public. Usually you keep your project private until you're ready to start recruiting volunteers and start working on project tasks.
Wiki URL: The URL for your project's wiki page. This field defaults to your project name. It's important to include a wiki page with information for project members.
Announcement Group: A Google Group created to send announcements to your project team. Using this list, members cannot reply to messages; only you can send messages. The information flows one-way only. When new members join the project, they are automatically added to this Google Group. For more information on Google Groups, see Google Groups integration with Tech Projects.
Discussion Group: A Google Group for discussing issues with your team. When new members join the project, they are automatically added to this Google Group.
Commits Group: A Google Group to stay updated about Subversion commits. When team members with a "Developer" role commit updates to the Subversion repository, a message is sent out to this group. The purpose of this group is to stay updated about the latest commits. When new members join the project, they are NOT automatically added to this Google Group.
Project URL: The site the project is focused on. For example, if the project is focused on creating a new website, include the website's URL here.
Version Control URL: The URL for the git or Subversion repository. Developers use this URL to upload software code to a git or Subversion repository.
Android package: If your project has Android package downloads, fill in the package name here. For example:
iOS package: If your project has iOS package downloads, fill in the package name here. For example:
Meeting Schedule: The days and times that your group regularly meets. Establishing a regular meeting time can be an important way to communicate with your project team members. You may want to mention things like the Google Groups above.

Depending on the nature of your project, you may not need all of these resources. However, they are available to you as part of the Tech community project framework.

As a project manager, you can edit this information at any time once the project has been created.

Note: Your project should remain private until you're ready to go public. Even though you may add information to each of these fields, you still need to define a body of work before you make your project public. After you define a body of work, you can then make your project public and start recruiting volunteers.

Create a Tech Forum

If beta testing is a primary focus, you may want to use the Tech Forum to gather feedback. The forum allows community members to post and respond to threads as much as they need. If you were to use your Google Group for this purpose, many community members may quickly grow tired of receiving so many e-mail messages.

The Beta Testing forums for projects provide a good example of forums in action. To create a new forum for your project, contact Tim Riker.

Create a wiki page

When you set up your project in Tech, you specified a URL for a wiki page. You now need to create the content for the wiki page. Your wiki page acts as a welcome page and includes key information about the project for incoming community members. Your wiki page might include the following details:

  • Description and purpose of the project
  • Time frames and deadlines for project milestones
  • Project resources and contacts
  • Guidelines and instruction
  • Test sites, roles, and versions
  • Expectations of volunteers
  • Meeting schedules

See TechWiki:Wiki editing tutorial and Guidelines for information about working with this wiki. The wiki is run on Mediawiki, which is the same platform as Wikipedia. If you search the web for Mediawiki help, most of the same information will apply here.

Define the skills needed for your project

When you set up a project, you can select the skills and expertise level that are needed for your project. The skills you define will later help you locate community members who have matching skills. Below your project, there's a section with skills to select. This will help match up your project needs with volunteer skillsets.

Once you have finished getting set up, you're ready to move on to the next step: 2. Define a body of work (project managers).

This page was last modified on 19 July 2019, at 16:02.

Note: Content found in this wiki may not always reflect official Church information.